Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, mikael(dot)kjellstrom(at)gmail(dot)com
Subject: Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
Date: 2024-04-06 06:02:23
Message-ID: 0843ebf1-744d-450f-9b95-c155cffc5523@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05.04.24 23:48, Daniel Gustafsson wrote:
> The reason to expand the check is to ensure that we have the version we want
> for both OpenSSL and LibreSSL, and deprecating OpenSSL versions isn't all that
> commonly done so having to change the version in the check didn't seem that
> invasive to me.

Why do we need to check for the versions at all? We should just check
for the functions we need. At least that's always been the normal
approach in configure.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2024-04-06 06:03:13 Re: remaining sql/json patches
Previous Message Andrey M. Borodin 2024-04-06 05:34:46 Re: Weird test mixup