Re: Fix use of openssl.path() if openssl isn't found - Mailing list pgsql-hackers

From Tristan Partin
Subject Re: Fix use of openssl.path() if openssl isn't found
Date
Msg-id CWT7EW1M207L.21UIKZ11LT0H@neon.tech
Whole thread Raw
In response to Re: Fix use of openssl.path() if openssl isn't found  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Fix use of openssl.path() if openssl isn't found
List 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

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Show WAL write and fsync stats in pg_stat_io
Next
From: Shlok Kyal
Date:
Subject: Re: [PoC] Implementation of distinct in Window Aggregates: take two