On Fri, Nov 16, 2007 at 09:04:38AM +0100, Peter Eisentraut wrote:
> Am Freitag, 16. November 2007 schrieb Tom Lane:
> > [ digs for a moment... ] According to my notes we are using autoconf
> > 2.53 for versions 7.3-8.0 and 2.59 for the later branches. So 2.13
> > is already out of the picture. It might be that 2.53 to 2.59 to 2.61
> > is not all that big a jump in reality, but I've got to say that it
> > scares me when I read commit-log entries that report ten thousand lines
> > worth of diffs in a 20K-line script ...
>
> Yeah, I think it's a bit insane. Keeping a few Autoconf versions around
> isn't
> hard at all. We have been doing it for years. (Hint: ./configure; make;
> make install)
Yeah.
I reiterate my point that I think it'd be good with a dedicated VM to build
the snapshots and releases off, that isn't affected by other changes to
whatever machine happens to be used. This VM could then be given all the
required autoconf versions, and it'd stay stable - and wouldn't be affected
by choices by whatever distribution is used.
Last time it was flex (or was it bison). This time autoconf (which I
beleive has happened before as well). It *will* happen again. If we move to
the latest autoconf now, it will just happen the next time <distro of
choice> upgrades what they have. (I say distro of choice. In thi case it's
freebsd, but I'm sure it happens on other platforms as well. For example, I
notice my Gutsy box has a different autoconf from my Dapper one. Which is
why I do my pg autoconf work on the dapper one)
//Magnus
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
