Re: pgsql: Further cleanup of autoconf output files for GSSAPI changes.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Further cleanup of autoconf output files for GSSAPI changes.
Date: 2023-04-17 20:25:52
Message-ID: 2511023.1681763152@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 2023-04-17 Mo 15:53, Tom Lane wrote:
>> (This three-build-system business can't go away soon enough.)

> From my POV we can remove it any time - I am still having Windows
> issues with meson, but only with MSYS2. The MSVC meson build on drongo
> is perfectly well behaved.

I think the outcome of the discussion a week or so ago was that
we want the MSVC scripts in v16, but we can nuke them from HEAD
as soon as the branch is made.

autoconf unfortunately will have to live a good bit longer ...
I don't think we're anywhere near the point where the meson
system is mature enough to drop that.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Jeff Davis 2023-04-17 20:46:24 pgsql: Comment fix for 60684dd834.
Previous Message Andrew Dunstan 2023-04-17 20:22:30 Re: pgsql: Further cleanup of autoconf output files for GSSAPI changes.

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2023-04-17 20:42:50 Re: optimize several list functions with SIMD intrinsics
Previous Message Andrew Dunstan 2023-04-17 20:22:30 Re: pgsql: Further cleanup of autoconf output files for GSSAPI changes.