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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Jacob Champion <jchampion(at)timescale(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
Date: 2023-06-02 21:21:54
Message-ID: ZHpGx8I5ifDUZPaP@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 02, 2023 at 10:35:43AM +0200, Daniel Gustafsson wrote:
> I think we should avoid the is-defined-in dance and just pull out the version
> numbers for comparisons. While it's true that LibreSSL doesn't play well with
> OpenSSL versions, they do define their own which can be checked for to
> distinguish the libraries.

Agreed. How about tackling that in a separate patch? At this stage,
I would like to not care about ./configure and do it only with meson,
but there is value in reporting the version number in ./configure to
see the version coverage in the buildfarm.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2023-06-02 21:23:19 Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
Previous Message Ankit Pandey 2023-06-02 19:42:32 [Question] pgwal increasing over max_wal_size