Re: Fix use of openssl.path() if openssl isn't found

From: "Tristan Partin" <tristan(at)neon(dot)tech>
To: "Michael Paquier" <michael(at)paquier(dot)xyz>
Cc: "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix use of openssl.path() if openssl isn't found
Date: 2023-11-08 06:07:49
Message-ID: CWT7EW1M207L.21UIKZ11LT0H@neon.tech
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue Nov 7, 2023 at 11:53 PM CST, Michael Paquier wrote:
> On Tue, Nov 07, 2023 at 04:06:56PM -0600, Tristan Partin wrote:
> > Found this issue during my Fedora 39 upgrade. Tested that uninstalling
> > openssl still allows the various ssl tests to run and succeed.
>
> Good catch. You are right that this is inconsistent with what we
> expect in the test.
>
> > +openssl_path = ''
> > +if openssl.found()
> > + openssl_path = openssl.path()
> > +endif
> > +
> > tests += {
> > 'name': 'ssl',
> > 'sd': meson.current_source_dir(),
> > @@ -7,7 +12,7 @@ tests += {
> > 'tap': {
> > 'env': {
> > 'with_ssl': ssl_library,
> > - 'OPENSSL': openssl.path(),
> > + 'OPENSSL': openssl_path,
> > },
> > 'tests': [
> > 't/001_ssltests.pl',
>
> Okay, that's a nit and it leads to the same result, but why not using
> the same one-liner style like all the other meson.build files that
> rely on optional commands? See pg_verifybackup, pg_dump, etc. That
> would be more consistent.

Because I forgot there were ternary statements in Meson :). Thanks for
the review. Here is v2.

--
Tristan Partin
Neon (https://neon.tech)

Attachment Content-Type Size
v2-0001-Fix-use-of-openssl.path-if-openssl-isn-t-found.patch text/x-patch 865 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shlok Kyal 2023-11-08 06:16:08 Re: [PoC] Implementation of distinct in Window Aggregates: take two
Previous Message Michael Paquier 2023-11-08 05:59:07 Re: Show WAL write and fsync stats in pg_stat_io