From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Changes to handling version numbers internally |
Date: | 2000-07-03 02:19:31 |
Message-ID: | Pine.BSF.4.21.0007022315460.833-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 2 Jul 2000, Tom Lane wrote:
> The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> >> This way we can also make it available to shell scripts and make
> >> files. The next autoconf version will have built-in support for this
> >> setup, so it's not like I'm making this up. :)
>
> > I see you've already committed the changes, which I still disagree with
> > ... I don't like the fact that someone has to remember to update the
> > configure.in and autoconf it to change the version number.
>
> It's a lot better than it was before ;-)
>
> > We already have the mess with template files, why not create a VERSION
> > file that could just as easily be read in by configure, without having
> > to do an autoconf, to change the version?
>
> Gilding the lily. The people who are likely to be bumping the version
> number are all perfectly familar with autoconf.
Ya, I've been fighting myself internally on this point ... I just hate the
though of embed'ng it into configure, that's all ...
peter mentioned something about next version of autoconf doing this?
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2000-07-03 03:57:56 | RE: pgsql/src/backend/postmaster (postmaster.c) |
Previous Message | Tom Lane | 2000-07-03 01:50:17 | Re: Changes to handling version numbers internally |