Hi Terrence, *, On Mon, Jul 20, 2009 at 6:45 PM, Terrence Miller<[email protected]> wrote: > > any source information needed to do a build should be in a source file and > stored locally.
No. That differs from system to system and thus cannot be stored in a sensible way. > Examples of information that should be in a source files are: > > - A list of all the packages which need to be installed in order for the > build to succeed. configure checks for that. If counfigure doesn't report any issues and your build still doesn't succeed, then it is a bug in configure that should be fixed. > (better yet a script which will put a system in the desired state.) Again, see above. > - the options specified to configure Don't know what you're up to here. options are options for the reason of being optionally turned on/off. So what sense does it make to hardcode options? You're free to keep your config.log / config.parms if you want to remember what configure options you used. > (both are distro specific). > > Also having any source files copied into external is (in my opinion) a > problem. For example, > the URL for gpc.[ch] could go dead overnight with no warning. gpc is no longer needed (for a looong time). > 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. Sorry, but again that is not doable. > 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: No. Use an appropriate, already configured virtual machine for that. > cd milestone; ./product_build > > Then she/he should be able to come back a year later and build the same > binaries. Why would you want to do that in the first place? A year later so much stuff has changed in the sources - why would you want to build such an old version then? ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
