Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1poVQD-0006GN-NU for pgsql-committers@arkaria.postgresql.org; Mon, 17 Apr 2023 20:25:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1poVQC-0005R2-IM for pgsql-committers@arkaria.postgresql.org; Mon, 17 Apr 2023 20:25:56 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1poVQC-0005Qt-BX for pgsql-committers@lists.postgresql.org; Mon, 17 Apr 2023 20:25:56 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1poVQ9-000NbG-Uy for pgsql-committers@lists.postgresql.org; Mon, 17 Apr 2023 20:25:55 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 33HKPq402511024; Mon, 17 Apr 2023 16:25:52 -0400 From: Tom Lane To: Andrew Dunstan cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Further cleanup of autoconf output files for GSSAPI changes. In-reply-to: <7d7dcc20-ba19-5340-9be8-f255e8b42edc@dunslane.net> References: <08dd6053-deee-52e9-954b-eb69232905c9@dunslane.net> <2506819.1681761221@sss.pgh.pa.us> <7d7dcc20-ba19-5340-9be8-f255e8b42edc@dunslane.net> Comments: In-reply-to Andrew Dunstan message dated "Mon, 17 Apr 2023 16:22:30 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2511022.1681763152.1@sss.pgh.pa.us> Date: Mon, 17 Apr 2023 16:25:52 -0400 Message-ID: <2511023.1681763152@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan 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