From: | "Matt Smith (matts3)" <matts3(at)cisco(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Meson install warnings when running postgres build from a sandbox |
Date: | 2025-10-22 23:27:47 |
Message-ID: | MW6PR11MB83109CA05534BA286DDBA57B8CF3A@MW6PR11MB8310.namprd11.prod.outlook.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)yesql(dot)se>
Sent: Wednesday, October 22, 2025 6:30 PM
To: Matt Smith (matts3) <matts3(at)cisco(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Meson install warnings when running postgres build from a sandbox
> On 22 Oct 2025, at 02:57, Matt Smith (matts3) <matts3(at)cisco(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2025-10-22 23:45:48 | Re: Add copyright notice to 048_vacuum_horizon_floor.pl |
Previous Message | Gurjeet Singh | 2025-10-22 23:17:40 | Git clone over git protocol fails |