From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
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 01:50:17 |
Message-ID: | 9245.962589017@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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. Also, we've already
got bad-enough problems with dependencies (see nearby thread) without
introducing a dependency from a file that's read by configure to
who-knows-where --- a dependency that can't be handled by 'make depend'.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2000-07-03 02:19:31 | Re: Changes to handling version numbers internally |
Previous Message | The Hermit Hacker | 2000-07-03 01:43:40 | Re: Built with PostgreSQL (images) |