Re: Improve prep_buildtree

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improve prep_buildtree
Date: 2025-07-30 15:37:38
Message-ID: CAOYmi+mFp6o2dw_P0=WVWGsXUHCKEgAqFMLFn1u0GyLWAjdUog@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 30, 2025 at 6:35 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> For this purpose, I think it's better for us to rely on things we
> control than things Meson controls. Adding a new top-level directory
> is rare enough that I don't see a problem with needing to update
> prep_buildtree.

+1. (This approach should also keep prep_buildtree from recursing into
my git worktrees and vpaths, so I'm excited to give it a try!)

--Jacob

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Xuneng Zhou 2025-07-30 15:42:10 Re: Add progressive backoff to XactLockTableWait functions
Previous Message Peter Eisentraut 2025-07-30 15:10:16 Re: Support getrandom() for pg_strong_random() source