From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH] Fix OAuth feature detection on OpenBSD+Meson |
Date: | 2025-06-24 20:43:14 |
Message-ID: | CAOYmi+=xdooCazXCK-6_4eEFccRh--EUq-qS0rkDOz_bPbnKqg@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 23, 2025 at 5:19 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> As far as I recall, we've always thought that autoconf's approach
> of "explicitly specify the features you expect to get" is the
> right way to do things. I don't love meson's default you-get-
> whatever-seems-available approach at all, though maybe that's
> my history as a package builder talking. I think not using that
> behavior would be a real good idea, at least for testing purposes.
For development I like "give me everything" by default, but for
testing and packaging I agree with you.
--Jacob
From | Date | Subject | |
---|---|---|---|
Next Message | Jacob Champion | 2025-06-24 20:46:04 | Re: [PATCH] Fix OAuth feature detection on OpenBSD+Meson |
Previous Message | Jacob Champion | 2025-06-24 20:39:49 | Re: [PATCH] Fix OAuth feature detection on OpenBSD+Meson |