From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
---|---|
To: | Nazir Bilal Yavuz <byavuz81(at)gmail(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-30 14:45:00 |
Message-ID: | CAOYmi+=zFMTZVNcM1z3E1W3mJ2e5Au-QW8v2dV-puUPxU1emCQ@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jun 25, 2025 at 3:46 AM Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> wrote:
> I wanted to experiment with it.
That was fast, thank you!
> First, I got the current list of
> features from upstream, then disabled the auto features, then
> explicitly enabled these features. I did this only for FreeBSD to show
> my idea roughly.
>
> There are two patches; 0001 disables auto features for all of the
> tasks and 0002 explicitly enables these features for FreeBSD.
Just from a stylistic perspective, I think I'd prefer for
`--auto-features=disabled` to be folded into the beginning of the
MESON_FEATURES variable. Or is there another reason to control them
fully independently?
Also: how do we ensure that none of the previously enabled features
were missed in this list, for all the OSes we've modified? (I'm a
Meson novice.)
> What do you think about this approach? If you are okay with this, I
> can apply it to all CI tasks (and possibly create another thread for
> it).
Seems good to me. I think a new top-level thread would be good too, to
get more eyes on the changes.
Thanks!
--Jacob
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2025-06-30 15:01:15 | Re: Improve error reporting in 027_stream_regress test |
Previous Message | Andres Freund | 2025-06-30 14:44:25 | Re: AIO v2.5 |