two OOo orig.tar.gzs?
-----BEGIN PGP SIGNED MESSAGE-----
now that the OpenOffice.org help is buildable with free Java (gcj/gij) I
want to move it to main (it's currently in contrib because it to now it
needed non-free jars and Sun/Blackdown/IBM Java to build.
But there's some fundamental problem here: the increased buildtime and
There's 13 help packages enabled; with the 12MB size of each this
makes alone 156 MB for the help. And the build time increases
drastically. Even only enabling the en-US help (which has to be done
anyway except when I get around to write a configure flag to disable
help bubilding ) extends the build with some hours. If you build all languages
enabled for the langpacks the help for them is built too and this makes
a buildtime for near 24h even on my Xeon 2.4Ghz 2GB RAM (with the OOo equivalent
of make -j2).....
Now, if I upload that with everything included (except the dictionaries which are
externally since some time anyway) the initial upload is 608 MB - including full
source - and every upload in which you may only have changed stuff which
affects the binaries and the "normal" arch-indep packages makes it a
upload size of around 411 MB (- orig.tar.gz). Just uploading the "normal" packages
would be far less. And the diff.gz of openoffice.org at the moment is 55 M(!)
mainly because of updated uuencoded GSI files for updating the
localizations. If the localizations were built from a seperate source
pakcage, the diff on the "normal" openoffice.org source package would
significantly decrease (a?though the GSIs then of course will be in the
- -l10n diff)
For overview, the packages as they currently are on my hd:
That's when the idea to split it was born. The idea is to split it into
an openoffice.org and a openoffice.org-l10n sourcepackage, both
unfortunately needing the same orig.tar.gz since for building the
langpacks you need to build the whole of OOo anyway with the same
openoffice.org then should build the "normal" arch-dep and arch-indep
packages (maybe including -help-en-us, but that also can be built from
l10n, -l10n-en-us is planned to go away and be merged back into -common)
and the language packs and the localized helps from openoffice.org-l10n,
decreasing the upload size of fixes not affecting the (localized) help
or the langpacks and also increasing the build time for "openoffice.org"
since not every language and the helpcontent2 for it is built anymore.
The decision to copy the source package has the disadvantage of
additional disk space for the .orig tarball, but improves both
build time and the size of single uploads (assuming that the -l10n
package is uploaded less often). In the end, this reduces the
amount of data which needs to be handled by mirrors. The total
space used for binary packages will be the same, as we are able to
remove the openoffice.org-help-* from contrib and will not be the full
source tarball size difference again since we already have a stripped-down
orig.tar.gz for the help in contrib. Before you ask, no I would like to *not*
use that since that one isn't integrated into the regular OOo building, translation
update etc scheme we have in Debian and is and will be maintainance nightmare if it
stays like it.
Ubuntu already does something similar; although for additionally
someother reasons (like the abbility to update translations
independently from openoffice.org). I'd merge dokos patch (maybe a bit
I asked Jörg on IRC about what he thinks about that and he said he
doesn't accept that but I should mail ftpmaster@ asking for comments.
That's why this mail is in your inbox now ;-)
Opinions? I'd like to upload OOo 2.0.2rcX to experimental soon...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
-----END PGP SIGNATURE-----