It seems the project() function's meson_version arg describes the minimum version required. From the docs<https://mesonbuild.com/Reference-manual_functions.html#project>
Takes a string describing which Meson version the project requires. Usually something like >=0.28.0. So perhaps a comment is the only option for now. Matt ________________________________ From: Matt Smith (matts3) <[email protected]> Sent: Thursday, October 23, 2025 10:27 AM To: Daniel Gustafsson <[email protected]> Cc: PostgreSQL Hackers <[email protected]> Subject: Re: Meson install warnings when running postgres build from a sandbox 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 <[email protected]> Sent: Wednesday, October 22, 2025 6:30 PM To: Matt Smith (matts3) <[email protected]> Cc: PostgreSQL Hackers <[email protected]> Subject: Re: Meson install warnings when running postgres build from a sandbox > On 22 Oct 2025, at 02:57, Matt Smith (matts3) <[email protected]> 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
