-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
- --On Sunday, June 08, 2008 21:27:03 -0400 Tom Lane <[EMAIL PROTECTED]> wrote: > Andrew Dunstan <[EMAIL PROTECTED]> writes: >> Tom Lane wrote: >>> I'm tempted to suggest letting the script invoke autoconf, too, >>> but that would require standardizing where to find the correct >>> version of autoconf for each branch; so it might not be such a >>> great idea. > >> Unfortunately that's true. Maybe we could agree on using an alias for >> the right version of autoconf, but it seems likely to be error prone. > > Actually, the way I do things is that my setup script for working > with each particular version tree includes adjusting $PATH so that > the right autoconf gets found just by saying "autoconf". If everyone > who might tag releases wanted to do it the same way, then we could > just let the script say "autoconf". But I'm not sure anybody else > likes that plan. What I was thinking was just to have the script > print out something like > > Tagged tree as 8.3.4 > Don't forget to run autoconf 2.59 before committing I like that one ... - -- Marc G. Fournier Hub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhMj4MACgkQ4QvfyHIvDvNWAACfeEuX8PCwbPgZLutpya859T+5 sDYAoKgTnLoypgDOwr4TSYVd+G5Dn+kn =Cl6d -----END PGP SIGNATURE----- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
