вÑ, 23 ноÑб. 2021 г. в 20:55, Neil Bowers <neilb@neilb.org>: > One approach is to bundle Net::SSLeay and IO::Socket::SSL, but I don't know if that's the best / right solution? > > One problem with bundling these modules is that we are then committed to ensuring that they work on all supported platforms / configurations. Is it ok to support https out-of-the-box on some supported platforms but not all of them? I think so. There exists (at least) one huge gotcha. openssl major api bump & rolling distros like arch/void. There will be situations when the distro already has an api-incompatible library, but even bleadperl still doesn't have an updated bindings, not starting to speak about x-1 release. So for a successful experience, both in-core tests and http layer over it should be ready for a complete compilation failures and subsequent module absence. I'd say that it should be it's own separate level of guarantees for those modules and their availability despite being bundled with core. Best regards, Sergey AleynikovThread Previous | Thread Next