Re: renaming configure.in to configure.ac

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: renaming configure.in to configure.ac
Date: 2020-07-15 13:45:54
Message-ID: 3057335.1594820754@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> It was mentioned elsewhere in passing that a new Autoconf release might
> be coming. That one will warn about the old naming "configure.in" and
> request "configure.ac". So we might want to rename that sometime.
> Before we get into the specifics, I suggest that all interested parties
> check whether buildfarm scripts, packaging scripts, etc. need to be
> adjusted for the newer name.

Along the same line, I read at [1]

Because it has been such a long time, and because some of the changes
potentially break existing Autoconf scripts, we are conducting a
public beta test before the final release of version 2.70. Please
test this beta with your autoconf scripts, and report any problems you
find to the Savannah bug tracker:

Maybe we should do some pro-active testing, rather than just waiting for
2.70 to get dropped on us? God knows how long it will be until 2.71.

regards, tom lane

[1] https://lists.gnu.org/archive/html/autoconf/2020-07/msg00006.html

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2020-07-15 13:47:25 Re: Improve handling of parameter differences in physical replication
Previous Message Andrew Dunstan 2020-07-15 13:39:11 Re: renaming configure.in to configure.ac