|From:||Daniel Gustafsson <daniel(at)yesql(dot)se>|
|To:||Michael Paquier <michael(at)paquier(dot)xyz>|
|Cc:||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~?|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
> On 26 May 2023, at 04:08, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Thu, May 25, 2023 at 10:16:27AM +0200, Daniel Gustafsson wrote:
>> The changes to the Windows buildsystem worry me a bit, but they don't move the
>> goalposts in either direction wrt to LibreSSL on Windows so for the purpose of
>> this patch we don't need to do more. Longer term we should either make
>> LibreSSL work on Windows builds, or explicitly not support it on Windows.
> Yes, I was wondering what to do about that in the long term. With the
> argument that the MSVC scripts may be gone over meson, it is not
> really appealing to dig into that.
Yeah, let's revisit this during the v17 cycle when the future of these scripts
will become clearer.
> Something that was missing in 0001 is the bump of OPENSSL_API_COMPAT
> in meson.build. This was in 0002.
> Please find attached an updated patch only for the removal of 1.0.1.
> Thanks for the review.
|Next Message||Alvaro Herrera||2023-05-26 08:56:53||Re: Cleaning up nbtree after logical decoding on standby work|
|Previous Message||Michael Paquier||2023-05-26 07:46:31||Re: Cleaning up nbtree after logical decoding on standby work|