Re: Meson install warnings when running postgres build from a sandbox

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
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
Date: 2025-10-22 07:30:27
Message-ID: 73627486-6BB3-4AF8-AC10-0F93E4D0B635@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-10-22 07:33:25 Re: Panic during xlog building with big values
Previous Message jian he 2025-10-22 07:20:21 Re: [PATCH] Add pg_get_policy_ddl() function to reconstruct CREATE POLICY statement