
On Monday, September 29, 2003, at 10:49 AM, Pug Bainter wrote:
Ricardo Kleemann (ricardo@americasnet.com) said something that sounded like:
Is there a way for mailman's configure script to detect the current settings (such as --with-username, --with-mail-gid and so on)?
Or is there a quick way for me to manually check what they should be?
I always keep my build directory for at least one version back. Because of that, I can look at the top of the config.status file to see how I called configure.
Not to one-up you but...
I record the steps I take to build something in a script, so that the
next time I build something I can edit the script a little and run it.
Lately I've added a boilerplate at the top that sets the PATH,
LD_LIBRARY_PATH and other variables so that things are 100% repeatable.
(You'd be surprised at the number of times I need to make subtle
changes to the PATH to get something to build.)
Eventually I made the editing easier by changing version numbers to variables, which are all set at the top of the script.
And not to brag, but you should see my BUILD_APACHE.sh script. It gets apache, php, mod_perl, checks the md5 checksums, builds everything, and does the install. And I only have to change variables at the top each time a new version is released.
I highly recommend this technique for anyone that upgrades UNIX packages frequently.
--tal