Build OOo langpacks separately from code

Registered by Matthias Klose on 2006-06-23

Build the OOo l10n and help packs in less CPU time, and without duplicating the OOo source in the archive.

Currently the archive hosts two (identical) 450MB OOo source packages to be able to build the l10n and help packages independently from the OOo packages containing the binaries. Do not build the code for binary packages when building language packages. The time required to build the language packages exceeds the time to build the binary packages.

We plan on trying to get this done via the split build in Jaunty+1 timeframe but will be working with Sun during the Jaunty release cycle to get upstream code ready for this.

Blueprint information

Status:
Complete
Approver:
Martin Pitt
Priority:
Low
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Started
Milestone target:
milestone icon later
Started by
Chris Cheney on 2008-06-25
Completed by
Martin Pitt on 2012-01-12

Related branches

Sprints

Whiteboard

Feb 9 - 11 - Meeting with Sun in Hamburg about split build

pitti, 2011-05-03: Launchpad support for *.sdf is not likely to happen, so let's re-unify -l10n back into libreoffice and avoid all the delta and pain.

doko, 2011-05-03: the former has nothing to do with the latter. the conversion scripts are present, but were not updated. yes, it would be a pain to have all the -l10n and -help builds in SRU's.

bjoern-michaelsen, 2011-05-03: sdf might or not might not die soon upstream anyway: http://wiki.documentfoundation.org/Development/Gsoc/Ideas#Translations_using_gettext -- with the death of OOo it will die rather sooner than later. Investing into sdf might end us with something obsolete upon delivery. If this is high priority, we should push forward the migration to gettext upstream as that is the most sustainable solution.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.