Christian Lohmaier wrote:
On Mon, Jul 20, 2009 at 6:45 PM, Terrence
Miller<[email protected]> wrote:
<SNIP>
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.
In current scheme you end up running configure once for each missing
package (since it stops on first error). Sometimes
the error message is useful but not always.
(better yet a script which will put a system in the desired state.)
Again, see above.
At least on Ubuntu there is a way to map from the name of a missing file
to the name of the package supplying
that file.
- 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?
A release is built with some fixed set of options. The documentation has
an example for Ubuntu 9.04 but gives no clue
what to do in any other situations. The wiki page is probably the wrong
place for multiple examples
You're free to keep your config.log / config.parms if you want to
remember what configure options you used.
(both are distro specific).
<SNIP>
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?
A critical bug in an old release has been reported by an important user
and the latest release contains a UI change the user
is unwilling to adopt.
ciao
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Terrence
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
