* Ralf Wildenhues wrote on Tue, Feb 07, 2006 at 07:08:37AM CET: > > You, the user, can still force variable assignments to be recorded even > for non-precious variables by putting them on the configure command > line: > ../source/configure FOO=bar > > So the bottom line is that you should always use this new notation if > dealing with Autoconf 2.50+ generated scripts. It's been pointed out to me that the English of my message may be inappropriate. I have not intended to annoy anyone, and would like to apologize if it was understood that way; keep in mind I am not a native speaker. Please read above as So the bottom line is that it is advantageous to always use this new notation if dealing with Autoconf 2.50+ generated scripts, as then configure can record this information easily; it will be easier for you to recreate the same configuration later. To give another useful example of this, happened to me yesterday: I updated a software package that uses a 2.13-generated configure script. I kept the build tree from the installation from more than 2.5 years ago, to be able to easily recreate a new build with identical features. It needed a couple of environment variables for this. Would this package use Autoconf-2.50+, it would have sufficed to keep the config.status file, and a simple ./config.status --version would have told me all that I needed. (Except that the upgrade broke some unrelated features anyway..) Cheers, Ralf _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
