Le 20/02/2013 00:14, Greg Troxel a écrit :
Guillaume Lasmayous <netbsd-lists%guigui2.net@localhost> writes:
Hello,
I'd like to remove security/py-ssh in the coming days.
I committed it when it was a dependency for sysutils/fabric.
Now that fabric has moved back to using security/py-paramiko, I
don't see
any reason to keep py-ssh around.
Any objections to removing it ?
I don't really understand the details, so my standard questions:
Are you saying that no user should reasonably want to use py-ssh? Is it
basically deprecated, with a dead upstream, and everyone useing it
should use paramiko instead? Just because a library-ish package has no
depending packages in pkgsrc is not a good enough reason to remove
something.
Of course, if you no longer want to maintain it, that's solely your
call.
Yes, basically, upstream declared py-ssh dead, pushing everybody
to use paramiko instead.
As stated on the github page (https://github.com/bitprophet/ssh/):
"This library started life as a fork of Paramiko but has now been
fully been merged back upstream.
As such, 'ssh' is defunct and will receive no future releases or
attention: please change your dependencies back to Paramiko,
and file any feature requests or bugfixes over on Paramiko's tracker."
G.
!DSPAM:1,5124c57d3141883415701!