![](https://secure.gravatar.com/avatar/30b3ac53296307ae5b47497280cc15df.jpg?s=120&d=mm&r=g)
Hi,
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 want to be able to upgrade mailman, but I never remember exactly what those settings should be, and since I have non-default settings, everytime I rebuild mailman, everything goes out of whack because I haven't specified the appropriate configuration.
----- Original Message Follows -----
http://mail.python.org/mailman/options/mailman-users/ricardo%40americasnet.c...
![](https://secure.gravatar.com/avatar/01aa7d6d4db83982a2f6dd363d0ee0f3.jpg?s=120&d=mm&r=g)
On Mon, 2003-09-29 at 10:37, Ricardo Kleemann wrote:
You can look in config.log (on some systems config.status). Look in the first bunch of lines and it will show you the options you used the last time you ran configure -- as long as you have your old source tree still around, of course!
-Barry
![](https://secure.gravatar.com/avatar/941f303545da2cef91c28713963c0c33.jpg?s=120&d=mm&r=g)
Ricardo Kleemann (ricardo@americasnet.com) said something that sounded like:
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.
Ciao,
-- Pug Bainter | AMD, Inc. System Engineer, MTS | Mail Stop 625 Pug.Bainter@amd.com | pug@pug.net | 5900 E. Ben White Blvd Phone: (512) 602-0364 | Fax: (512) 602-6970 | Austin, TX 78741 Note: The views may not reflect my employers, or even my own for that matter.
![](https://secure.gravatar.com/avatar/ba2048541a79d22d6892f54c9298a717.jpg?s=120&d=mm&r=g)
On Monday, September 29, 2003, at 10:49 AM, Pug Bainter wrote:
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
![](https://secure.gravatar.com/avatar/5d1f57b8e61bd61ebb2b77ede705767d.jpg?s=120&d=mm&r=g)
"TL" == Tom Limoncelli <tal@whatexit.org> writes:
TL> And not to brag, but you should see my BUILD_APACHE.sh script. It gets TL> apache, php, mod_perl, checks the md5 checksums, builds everything, and TL> does the install. And I only have to change variables at the top each TL> time a new version is released.
Almost sounds like freebsd's ports system ;-)
Personally, for stuff I don't build from ports with default settings, I just keep notes in a text file on what I did.
Documentation... who'd a thunk it?
--
Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
![](https://secure.gravatar.com/avatar/01aa7d6d4db83982a2f6dd363d0ee0f3.jpg?s=120&d=mm&r=g)
On Mon, 2003-09-29 at 10:37, Ricardo Kleemann wrote:
You can look in config.log (on some systems config.status). Look in the first bunch of lines and it will show you the options you used the last time you ran configure -- as long as you have your old source tree still around, of course!
-Barry
![](https://secure.gravatar.com/avatar/941f303545da2cef91c28713963c0c33.jpg?s=120&d=mm&r=g)
Ricardo Kleemann (ricardo@americasnet.com) said something that sounded like:
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.
Ciao,
-- Pug Bainter | AMD, Inc. System Engineer, MTS | Mail Stop 625 Pug.Bainter@amd.com | pug@pug.net | 5900 E. Ben White Blvd Phone: (512) 602-0364 | Fax: (512) 602-6970 | Austin, TX 78741 Note: The views may not reflect my employers, or even my own for that matter.
![](https://secure.gravatar.com/avatar/ba2048541a79d22d6892f54c9298a717.jpg?s=120&d=mm&r=g)
On Monday, September 29, 2003, at 10:49 AM, Pug Bainter wrote:
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
![](https://secure.gravatar.com/avatar/5d1f57b8e61bd61ebb2b77ede705767d.jpg?s=120&d=mm&r=g)
"TL" == Tom Limoncelli <tal@whatexit.org> writes:
TL> And not to brag, but you should see my BUILD_APACHE.sh script. It gets TL> apache, php, mod_perl, checks the md5 checksums, builds everything, and TL> does the install. And I only have to change variables at the top each TL> time a new version is released.
Almost sounds like freebsd's ports system ;-)
Personally, for stuff I don't build from ports with default settings, I just keep notes in a text file on what I did.
Documentation... who'd a thunk it?
--
Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
participants (6)
-
Barry Warsaw
-
Chris Linstruth
-
Pug Bainter
-
Ricardo Kleemann
-
Tom Limoncelli
-
Vivek Khera