On Fri, Oct 12, 2012 at 12:50:42PM +0100, Nigel Taylor wrote:
> 'LWP::Protocol::https' => '6.02',
> Note the new requirement...
I have seen that. But that looks strange to me.
LWP::Protocol::https is listed as prerequisite by Crypt::SSLeay.
www/p5-libwww provides LWP::Protocol::https and has
security/p5-Crypt-SSLeay as run and build dependency.
The Crypt::SSLeay documentation says
The "Crypt::SSLeay" package provides "Net::SSL", which is loaded by
"LWP::Protocol::https" for https requests and provides the necessary
SSL glue.
This sounds like upstream got the dependencys the wrong way around.
So I decided to put www/p5-libwww only into the regress dependencies
of security/p5-Crypt-SSLeay.
With network_tests disabled, the regression Tests of p5-Crypt-SSLeay
pass. That is better than before. Also the p5-libwww tests pass.
LWP::Protocol::https is not used by Crypt::SSLeay.
When I enable network_tests, the incompatible LWP::Protocol::https
becomes obvious.
I updated p5-Crypt-SSLeay because some other perl programm failed
while loading the module. Now at least that is fixed for me.
> Then for LWP::Protocols::https v6.03
> PREREQ_PM => {
> 'LWP::UserAgent' => '6.04',
> 'Net::HTTPS' => 6,
> 'IO::Socket::SSL' => "1.54",
> 'Mozilla::CA' => "20110101",
> },
>
> LWP::UserAgent comes from p5-libwww and requires v6.04 or later.
> Net::HTTPS v6 is part of the split out Net-HTTP v6 (latest is v6.03)
> from p5-libwww.
>
> The whole set of updates is not ready, and requires checking through a
> large number of ports.
$ grep p5-libwww /usr/ports/INDEX | wc -l
91
I see the problem. But I think we have to step forward. Do you
have any plan in which small steps we can do the updates?
bluhm
