On Fri, Jan 22, 2016 at 12:58:56PM +0100, Landry Breuil wrote: > On Fri, Jan 22, 2016 at 11:31:38AM +0000, Nigel Taylor wrote: > > > > > > On 01/20/16 09:03, Mark Patruck wrote: > > > Update www/p5-Mojo to 6.40. > > > > > > - since 6.33 www/p5-Mojo depends on IO::Socket::IP 0.37 and according > > > to afresh1@ we won't get Perl 5.22.1 before the lock, so i've restored > > > net/p5-IO-Socket-IP from the attic (the patch is obsolete as fixed up- > > > stream) > > > > > > I've also updated ports/net/Makefile...diff is below > > > > > > > Obvious No from me, needs a lot more to convince me. > > > > p5-IO-Socket-Socks 0.67 requires IO::Socket::IP 0.37 but has been held > > back at 0.65. The only way to update IO::Socket::IP is in the core, > > followed by extensive tests. Having two possible IO::Socket:IP during > > builds / runtime means testing twice. This is not the same as just > > moving a port to a new version. You need not only to bring back > > IO::Socket::IP but everything related and move it forward, to it so it's > > an incomplete change. > > I dont see the issue with readding IO::Socket::IP 0.37 in the portstree, > since .. it was there before, and the ports using it were working fine > with it. It's not like there have been tremendous changes between 0.37 > and 0.29 > (http://cpansearch.perl.org/src/PEVANS/IO-Socket-IP-0.37/Changes) and it > will come with perl 5.22 anyway.
Fwiw, the requirement in mojo was bumped in https://github.com/kraih/mojo/commit/c0342de13c9c52ad963683018e56a0558f452517 Landry
