Re: meson and check-tests - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: meson and check-tests
Date
Msg-id f9196ed1-a0bd-406b-9899-30f21699f7ad@dunslane.net
Whole thread Raw
In response to Re: meson and check-tests  (Bilal Yavuz <byavuz81@gmail.com>)
Responses Re: meson and check-tests
List pgsql-hackers


On 2025-12-08 Mo 3:12 AM, Bilal Yavuz wrote:
Hi,

On Mon, 1 Dec 2025 at 06:33, Ashutosh Bapat
<ashutosh.bapat.oss@gmail.com> wrote:
On Sun, Nov 30, 2025 at 11:39 PM Andrew Dunstan <andrew@dunslane.net> wrote:

On 2025-11-27 Th 5:19 AM, Nazir Bilal Yavuz wrote:
Hi,

On Sat, 22 Nov 2025 at 01:16, Andrew Dunstan <andrew@dunslane.net> wrote:
Committed
Here is a small follow-up commit for documenting this feature.


This really belongs in the "meson" section. We need to add a new para
there similar to the "make" section para you are trying to amend here.


+1. I think we should follow a structure similar to the chapter
"installation from source code" which has a separate section for meson
at the same level as 'make and autoconf'.
Done in v2.


Thanks, that's better. But I'm wondering if this section shouldn't be moved to regress.sgml, alongside the equivalent for configure style builds, and linked to from here in the same way.


Maybe that's a topic for another day.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: Periodic authorization expiration checks using GoAway message
Next
From: Peter Smith
Date:
Subject: Re: DOCS - Clarify the publication 'publish_via_partition_root' default value.