develooper Front page | perl.perl5.porters | Postings from December 2021

Re: Pre-RFC: support https out-of-the-box

Thread Previous | Thread Next
From:
Craig A. Berry
Date:
December 2, 2021 13:39
Subject:
Re: Pre-RFC: support https out-of-the-box
Message ID:
CA+vYcVwV5qtkv8ZG1EZwwuX+fKOzgA8d30=36+1musSCwgDkZw@mail.gmail.com
On Wed, Dec 1, 2021 at 7:55 PM Ricardo Signes <perl.p5p@rjbs.manxome.org> wrote:
>
> On Wed, Dec 1, 2021, at 8:08 PM, Yuki Kimoto wrote:
>
> Suppose the Perl core contains Net::SSLeay.
>
> In this case, Net::SSLeay is already installed without the OpenSSL library and the tests of Net::SSLeay are not yet done.
>
> How do we test for correctness of behavior of Net::SSLeay?
>
>
> We would only build, test, and install Net::SSLeay if openssl was available.

I agree this is what we would want to do, with the "extensions"
Configure variable just not including Net::SSLeay if we couldn't
locate the SSL library at Configure time.  It might be a trickier case
than any we've had before, though.  The Makefile.PL for Net::SSLeay:

https://github.com/radiator-software/p5-net-ssleay/blob/master/Makefile.PL

goes through all sorts of gyrations to locate the OpenSSL or LibreSSL
libraries and headers in their platform-specific hiding places, which
tend to move around with library and platform releases.  It would be a
shame to have to copy and then maintain separately all of that logic
in Configure, but offhand I'm not sure how else we would do it.

Also note that Net::SSLeay requires Perl to be built with the same
compiler and options as (Open|Libre)SSL. Which would probably be
uneventful in many cases but could lead to a new flavor of bug report
in others.

Not trying to throw sand in the gears, but just trying to identify the
sand that will get in anyway.

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About