Hi!
I think that the truth is in between. OpenOffice really needs alot of
upstream type work. One of them is a build infrastructure that works.
It is really not very meaningful to package OpenOffice as it is now:
I guess there is a long-long list of lintian errors. However it might be good
for the
Hello!
I want to say, that you're talking about big problems that can happen
in future. We need to make usable openoffice packages now. Frankly
speaking, openoffice package that I've released on ~nidd/debian/unstable
is buildable by autobuilder.
If you could help us with making this package
* Jan-Hendrik Palic <[EMAIL PROTECTED]> [011028 12:33]:
> Peter has made a picture [2] with the builddependency- tree, that shows us,
> splitting the source is impossible.
> [2] http://www.altlinux.ru/~nidd/oo/oo-components-depends.psz
Wow, I had expected an much more complex tree. If you remove e
Matthias Klose wrote:
Jan-Hendrik Palic writes:
The change from javac to gcj is the next problem. gcj will not be able
to compile the javasource in openoffice, kaffe isn't it to.
If anyone knows a solution, please tell us!
would gcj from the HEAD branch (3.1) a solution?
I was talking ab
Jan-Hendrik Palic writes:
> The change from javac to gcj is the next problem. gcj will not be able
> to compile the javasource in openoffice, kaffe isn't it to.
> If anyone knows a solution, please tell us!
would gcj from the HEAD branch (3.1) a solution?
Hi all,
the last days, we work hard on OpenOffice:
Peter Novodvorsky ([EMAIL PROTECTED]) made a first package [1] of OpenOffice
depending on OpenOffice 638c. Be carefull, it is one package but it is
a beginning.
Bastian Blank ([EMAIL PROTECTED]) was working on the support for gcc-3.0
in OpenOf
6 matches
Mail list logo
