Re: [PATCH] Fix OAuth feature detection on OpenBSD+Meson

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
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 00:19:48
Message-ID: 819892.1750724388@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> writes:
> As a potential follow-up, is there any interest in switching the
> Cirrus Meson setup to explicitly enable the features that we expect to
> test? That would match what we do for Autoconf, I think; it would have
> helped me catch my mistake earlier.

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-06-24 01:18:18 Re: Fixes inconsistent behavior in vacuum when it processes multiple relations
Previous Message Jacob Champion 2025-06-24 00:06:27 Re: Tags in the commitfest app: How to use them and what tags to add?