On Sat, 14 Jan 2023 01:59:46 +0100
Graham Knop <haarg@haarg.org> wrote:
> On Fri, Jan 13, 2023 at 7:04 PM Paul "LeoNerd" Evans
> <leonerd@leonerd.org.uk> wrote:
> > Things bundled into cpan/ are built by perl's own build system while
> > basically ignoring the actual configure- and build-time
> > instructions of that module. This makes it very complicated to do
> > things like optional configurations, etc.. It would be difficult to
> > get Net::SSLeay to work with that.
>
> This seems like a misunderstanding or something. The configure and
> build instructions of dists in cpan/ are not ignored. If a dist in
> cpan/ includes a Makefile.PL, that file is used to configure and build
> the dist. I'm pretty sure that doesn't have anything to do with why
> Net::SSLeay is not included in core.
Ah, perhaps I have misremembered then. I remember when I wanted to add
a bunch of symbols to Socket so that IO::Socket::IP could use them
while being moved to core, it was all very complicated. Socket's own
Makefile.PL couldn't perform configure-like tests; it had to rely on
core's own configure mechanisms to tell it such answers as whether the
system C library has an `inet_pton()` function.
I may therefore be under the misapprehension that all bundled modules
have that restriction. If they don't, then great - it sounds like it
would be even easier to bundle Net::SSLeay into core than I had first
imagined. :)
If that reason isn't in the way, then I don't see why we can't at least
have an attempt at just bundling Net::SSLeay + IO::Socket::SSL with
perl, and see if it works.
Has anyone thought to just try it? ;)
--
Paul "LeoNerd" Evans
leonerd@leonerd.org.uk | https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/
Graham Knop <haarg@haarg.org> wrote:
> On Fri, Jan 13, 2023 at 7:04 PM Paul "LeoNerd" Evans
> <leonerd@leonerd.org.uk> wrote:
> > Things bundled into cpan/ are built by perl's own build system while
> > basically ignoring the actual configure- and build-time
> > instructions of that module. This makes it very complicated to do
> > things like optional configurations, etc.. It would be difficult to
> > get Net::SSLeay to work with that.
>
> This seems like a misunderstanding or something. The configure and
> build instructions of dists in cpan/ are not ignored. If a dist in
> cpan/ includes a Makefile.PL, that file is used to configure and build
> the dist. I'm pretty sure that doesn't have anything to do with why
> Net::SSLeay is not included in core.
Ah, perhaps I have misremembered then. I remember when I wanted to add
a bunch of symbols to Socket so that IO::Socket::IP could use them
while being moved to core, it was all very complicated. Socket's own
Makefile.PL couldn't perform configure-like tests; it had to rely on
core's own configure mechanisms to tell it such answers as whether the
system C library has an `inet_pton()` function.
I may therefore be under the misapprehension that all bundled modules
have that restriction. If they don't, then great - it sounds like it
would be even easier to bundle Net::SSLeay into core than I had first
imagined. :)
If that reason isn't in the way, then I don't see why we can't at least
have an attempt at just bundling Net::SSLeay + IO::Socket::SSL with
perl, and see if it works.
Has anyone thought to just try it? ;)
--
Paul "LeoNerd" Evans
leonerd@leonerd.org.uk | https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/