From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: renaming configure.in to configure.ac |
Date: | 2020-07-16 04:56:39 |
Message-ID: | 20200716045639.GD415411@rfd.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 15, 2020 at 09:45:54AM -0400, Tom Lane wrote:
> 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.
Sounds good. A cheap option would be to regenerate with 2.70, push that on a
Friday night to see what the buildfarm thinks, and revert it on Sunday night.
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2020-07-16 05:47:10 | Re: Transactions involving multiple postgres foreign servers, take 2 |
Previous Message | Etsuro Fujita | 2020-07-16 04:55:48 | Re: Partitioning and postgres_fdw optimisations for multi-tenancy |