Terrence Miller wrote: > If OOo wants to be able to reproduce builds, we will need to have a > local snapshot of any package > listed as a build requirement. > > The idea is that QA person should be be able to take a blank machine, a > Linux install CD, > and a CD containning a milestone and after doing an install and loading > the second CD do only: > > cd milestone; ./product_build > > Then she/he should be able to come back a year later and build the same > binaries.
hmmm... it seems to me that what you want is what our release engineering team calls the "baseline". this is basically the standard stuff that lives in /usr/include (only those things that really are standard across all distributions and come with backward compatibility guarantees), with assorted binaries, libraries, and of course the toolchain (compiler, linker, etc.). unfortunately, the exact composition of that "baseline" for OOo is not publicly documented; only release engineering knows what's really in it. everything that is not guaranteed to be standard across all distributions is in the modules in the "external" project. but for developers, the baseline is actually not really needed; afaik it is most important for doing releases that are binary compatible (for the parts of OOo where that is important) and that work on all semi-recent linux distributions. (of course, there are also baselines for the other platforms) an unfortunate aspect of the OOo build system is that there are actually two entirely different ways to configure it: one way is via autoconf/configure, the other one with special "setsolar" tool that only works in Sun Hamburg network; i believe release engineering is currently planning to or working on using configure everywhere: that would mean less stuff to maintain and keep in sync. regards, michael -- A novice was trying to fix a broken Lisp machine by turning the power off and on. Knight, seeing what the student was doing, spoke sternly: "You cannot fix a machine by just power-cycling it with no understanding of what is going wrong." Knight turned the machine off and on. The machine worked. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
