Ooo-build

ooo-build

This collection of patches and build infrastructure exists solely as a reflection of the many problems encouraging reasonably responsive change up-stream. The process of change is painful for any organisation, the larger the more painful. However - the size of the problem is no excuse to not try; hence the evenutal aim is to remove the need for ooo-build by incrementally fixing the various problems.

About ooo-build

ooo-build arose from acute frustration with the bad-old days of OO.o process before the Child Workspace concept was introduced, it is also fueled by incredibly non-performant CVS server provided by collab.net.

remaining unsolved issue summary

A helpful summary of these is provided here in no particular order along with suggestions for improvement. Many of these are mercifully easy to fix, and should be fixed soon.

source hanlding

src packaging

We have habitually split the source into several pieces to aid downloading. The process of achieving this is codified in a simple shell-script [here]. It is probable that up-stream release source archives for each milestone in a timely fashion - but having used them it's not clear to me where they arrive. (FIX-ME).

src download

ooo-build has a post-configure 'download' mechanism, whereby the relevant source archives will be automatically downloaded to your system having configured it, in response to your various options.

cvs slowness

It can take multiple hours to tag (once) the full up-stream CVS; this is not conducive to some of the more funky 'nested workspace' ideas based on the CWS tooling becoming a reality. Adding large modules to a cws currently takes way too long. Interestingly, it's can be quicker to do a $ cvs diff, create a new cws and apply the patch than re-sync a cws. It also helps to have the diff in hand in case the cws tools fail mid-flow, since that has been known to loose data.