| Subject: | Unnecessary Crypt::SSLeay dependency |
The Crypt::SSLeay dependency makes this module hard to install on some systems. Starting with version LWP 6.02 https support is handled via LWP::Protocol::https. This module decides which SSL implementation to use.
This message is generated when installing Crypt::SSLeay (or read https://metacpan.org/pod/Crypt::SSLeay#DO-YOU-NEED-Crypt::SSLeay for more detailed reasoning)
*** THIS IS NOT AN ERROR, JUST A MESSAGE FOR YOUR INFORMATION ***
Do you really need Crypt::SSLeay?
Starting with version 6.02 of LWP, https support was unbundled into
LWP::Protocol::https. This module specifies as one of its prerequisites
IO::Socket::SSL which is automatically used by LWP::UserAgent unless
this preference is overridden separately. IO::Socket::SSL is a more
complete implementation, and, crucially, it allows hostname
verification. Crypt::SSLeay does not support this. At this point,
Crypt::SSLeay is maintained to support existing software that already
depends on it.
However, it is possible that your software does not really depend on
Crypt::SSLeay, only on the ability of LWP::UserAgent class to
communicate with sites over SSL/TLS.
If are using version LWP 6.02 or later, and therefore have installed
LWP::Protocol::https and its dependencies, and do not explicitly use
Net::SSL before loading LWP::UserAgent, or override the default socket
class, you are probably using IO::Socket::SSL and do not really need
Crypt::SSLeay.
Before installing Crypt::SSLeay, you may want to try specifying a
dependency on LWP::Protocol::https.
So in this case it would be sufficient to remove the explicit Crypt::SSLeay dependency from the module and makefile and add LWP::Protocol::https to the makefile instead