From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: On aclocal.m4 |
Date: | 2000-06-12 15:14:48 |
Message-ID: | 811.960822888@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> aclocal comes with automake as does the AM_PROG_MISSING macro that
> configure uses now. Note that this does not mean that anyone working on
> configure.in needs to have automake installed, only those that are adding
> external macro definitions.
... or editing existing ones to fix bugs ... in practice, as you push
more of configure's functionality into macros (which I agree is nice
from a readability standpoint) it will become almost impossible to work
on configure without modifying config/*.m4.
As things stood over the weekend, even just pulling from CVS required
automake, since aclocal.m4 may or may not get a newer timestamp than
the config/*.m4 files. I temporarily diked out the toplevel make
dependencies that tried to update aclocal.m4, but the issue needs
discussion.
I'd like to be convinced that automake is actually going to be a win
for Postgres before we start requiring developers to have it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-06-12 15:29:59 | Re: Patch for 'Not to stuff everything as files in a single directory, hash dirs' |
Previous Message | Karel Zak | 2000-06-12 15:05:26 | the contrib |