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 unit radix end user, who cannot download and install it for herself. But I regard it only as a placebo effort until the Real Thing happens.
A levelezőm azt hiszi, hogy Peter Novodvorsky a következőeket írta: > 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. Okay, so we have a usable openoffice package. The next step is to come up with a maintaineable one:) > > I still think splitting the source in packages is the way to go for > > OOo in the long run. Upstream is modular, and reflecting this in > > the packaging will help the builders and perhaps allowing other > > odk-software to be packages easily. (If it will exist some day). > > Please, can you be more verbose? I still don't understand why splitting > source in several source packages will help. It won't help autobuilders > anyhow. I don't see any matter to do it, and it is quite hard to do. > Could describe your point of view in details? There are a lot of externalia and cross-package wormholes in the oo source. The easyest way to get rid of them is to separate the packages, so the externalia drop out, and the cross-package nastynesses turn out. -- GNU GPL: csak tiszta forrásból
