Hi Ruediger, On Monday 08 October 2007 17:36, Rüdiger Timm wrote:
> > During the OOoCon, Petr had a presentation about the OOo package > > splitting. The most important part for a (Linux) package maintainer was > > to be able to build parts of OpenOffice.org separately; the thing is that > > with all the localizations, we are unable to get the build times under > > some 7 hours. But the build could be done nicely in parallel (on the > > level of machines, not processors) if the sources were split correctly, > > with correct rpms and -devel rpms [of course, applies to debs as well > > ;-)]. And of course, the -noarch > > Sorry, I do not understand this. How do you want to build f.e. > ooo-bootstrap, ooo-libs-core, and ooo-apps-writer in parrallel? > Bootstrap stuff like dmake or solenv is needed everywhere. Building > writer needs nearly all lower libraries in place. Sorry, it seems I should have been more verbose. As you can see below, I don't want these particular build in parallel, their order is fixed: > > ooo-bootstrap > > ooo-libs-3rdparty > > ure > > ooo-libs-guitoolkit > > ooo-libs-core And from this point: > > [the rest in whatever sequence/in parallel] It's the ooo-apps-writer, ooo-apps-calc, ... ooo-l10n that could be built in parallel and on different machines. Why don't I want to merge the 'fixed order' ones into one module? Simply 'divide et impera' ;-) They contain stuff that belongs more or less logically together. Eg. I believe we can shrink ooo-libs-core by just making some things better, but it's hard to start when one is overwhelmed by the amount of modules. Regards, Jan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
