Re: meson: Non-feature feature options - Mailing list pgsql-hackers

From Nazir Bilal Yavuz
Subject Re: meson: Non-feature feature options
Date
Msg-id CAN55FZ3GLXkWHpVwwU=OpLxid2vjSSsvrpW8MRPMWzC3JRvD5w@mail.gmail.com
Whole thread Raw
In response to Re: meson: Non-feature feature options  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: meson: Non-feature feature options  (Daniel Gustafsson <daniel@yesql.se>)
Re: meson: Non-feature feature options  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
Hi,

On Thu, 9 Mar 2023 at 16:54, Daniel Gustafsson <daniel@yesql.se> wrote:
>
> > On 9 Mar 2023, at 14:45, Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote:
>
> > How about we just hardcode "openssl" here instead?  We could build that array dynamically, of course, but maybe we
leavethat until we actually have a need?
 
>
> At least for 16 keeping it hardcoded is an entirely safe bet so +1 for leaving
> additional complexity for when needed.

We already have the 'ssl_library' variable. Can't we use that instead
of hardcoding 'openssl'? e.g:

summary(
  {
    'ssl': ssl.found() ? [ssl, '(@0@)'.format(ssl_library)] : ssl,
  },
  section: 'External libraries',
  list_sep: ', ',
)

And it will output:
ssl                    : YES 3.0.8, (openssl)

I don't think that using 'ssl_library' will increase the complexity.

Regards,
Nazir Bilal Yavuz
Microsoft



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: meson: Non-feature feature options
Next
From: Robert Haas
Date:
Subject: Re: postgres_fdw, dblink, and CREATE SUBSCRIPTION security