On Sat, Sep 19, 2020 at 02:22:51PM -0400, Kurt Mosiejczuk wrote: > On Sat, Sep 19, 2020 at 08:00:41PM +0200, Solène Rapenne wrote: > > > > Remove it? > > > Why remove it? Because it's python2? Do we have a python2 expiration > > policy? (I see others OS have a deadline for python2 removal, maybe > > we should do the same) > > It's python2. > It's not available from its author, only from our mirror of the distfile > on ftp.openbsd. > It parses packets and hasn't been updated. > > > If it works and that we don't have alternative in ports I think > > we should keep it. > > If folks *use* it, I'm ok with keeping it. However, it was imported more > than 11 years ago and hasn't been updated. It's homepage advises others to > use a different project. The source file isn't available. > > Honestly, the more I investigate this, the *less* I'd like it to stay. > > > There is a python3 pcapdiff at https://github.com/isginf/pcap-diff > > I don't know if it's a fork of net/pcapdiff though. > > Someone could do a port of that. It also depends on net/py-pcapy and sooner or^Wthan later Python 2 will go which means this dependency will go as well.
If actual *users* object we can postpone removal, but if noone barks I see no point in keeping cruft like this - I'd even argue that removing the legacy version would encourage users to port the new Python 3 version. OK kn
