I am about half way through my first build and have already run into things
which could lead to unstable Linux builds: My experience has convinced
me that
any source information needed to do a build should be in a source file
and stored locally.
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.
(better yet a script which will put a system in the desired state.)
- the options specified to configure
(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.
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.
Terrence Miller
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
