Re: Meson install warnings when running postgres build from a sandbox - Mailing list pgsql-hackers

From Matt Smith (matts3)
Subject Re: Meson install warnings when running postgres build from a sandbox
Date
Msg-id MW6PR11MB83109CA05534BA286DDBA57B8CF3A@MW6PR11MB8310.namprd11.prod.outlook.com
Whole thread Raw
In response to Re: Meson install warnings when running postgres build from a sandbox  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
I'm not sure what that comment would say.

Should there be such a thing as a maximum meson version that postgres supports?

Matt

From: Daniel Gustafsson <daniel@yesql.se>
Sent: Wednesday, October 22, 2025 6:30 PM
To: Matt Smith (matts3) <matts3@cisco.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Meson install warnings when running postgres build from a sandbox
 
> On 22 Oct 2025, at 02:57, Matt Smith (matts3) <matts3@cisco.com> wrote:

> This is all ok for now, but I'm wondering if meson changes the default behavior in a future version, how postgres would be able to support the old way of following symlinks with said future version.

Do you think it would be appropriate/helpful to add a comment for the future in
the project() portion of meson.build, where we already comment on meson
versions?

--
Daniel Gustafsson

pgsql-hackers by date:

Previous
From: Gurjeet Singh
Date:
Subject: Git clone over git protocol fails
Next
From: Masahiko Sawada
Date:
Subject: Re: Add copyright notice to 048_vacuum_horizon_floor.pl