From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
cc: pgsql-hackers@lists.postgresql.org
Subject: Re: PSA: Autoconf has risen from the dead
In-reply-to: <652d5f5d-27e7-b1db-03e0-c74cfdca40cd@enterprisedb.com>
References: <1627398.1642955357@sss.pgh.pa.us> <652d5f5d-27e7-b1db-03e0-c74cfdca40cd@enterprisedb.com>
Comments: In-reply-to Peter Eisentraut <peter.eisentraut@enterprisedb.com>
	message dated "Mon, 24 Jan 2022 09:11:52 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1871564.1643033667.1@sss.pgh.pa.us>
Date: Mon, 24 Jan 2022 09:14:27 -0500
Message-ID: <1871565.1643033667@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1871565.1643033667%40sss.pgh.pa.us>
Precedence: bulk

Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
> I have patches ready for this at 
> https://github.com/petere/postgresql/tree/autoconf-updates.
> My thinking was to wait until Autoconf 2.71 has trickled down into the 
> OS versions that developers are likely to use.

I find that kind of irrelevant, because we expect people to install
autoconf from source anyway to avoid distro-specific behavior.
I suppose that waiting for it to get out into the wild might be good
from the standpoint of being sure it's bug-free, though.

Do these versions fix any bugs that affect us (i.e., that we've
not already created workarounds for)?

			regards, tom lane