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 regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers