are outdated. ok benoit@ ajacoutot@
These are library classes written in PHP for various functionality and
used to be needed to support PHP applications in the ports tree (things
like roundcube, horde and others used them) but all of this type of
software in ports now uses bundled dependencies. For development,
typically a language-specific dependency manager (like www/composer)
is used rather than OS packages.
www/pear (providing pear itself and pear-utils) is still kept.
py2-only ports providing py-* modules that are no longer used in ports.
this doesn't change ports used to support standalone py2-only applications,
not currently planned to remove those at least until a few things with no
real alternatives get ported to py3.
which aren't used as dependencies in ports. many are either old stuff,
or things used to provide backports of functionality from newer Python
base versions which were used in ports that have already been converted
to py3-only.
@pkgpath markers). it is not a direct upgrade (config locations have
been rearranged) so add an @ask-update guard only shown to any users who
are still running 2.x pointing at the upstream information and giving a
chance to bail out.
No release from upstream since 2004, no IPv6 support and the port now fails
to build with "-fno-common".
There's net/scapy in our tree which can do everything that nemesis does and
more.
OK bcallah
Our packaged 1.0 version seems to be the last one that can be fetched
from upstream, which is long dead; HOMEPAGE http://packit.sf.net points
to a generic corporate stub.
FreeBSD packages an "updated" version, see
https://github.com/resurrecting-open-source-projects/packit/blob/master/ChangeLog
which effectively is the old source could with all readily available
distribution patches from Debian, Gento, etc. applied on top; other than
that there's no development, the project README explicitly asks for help
from actual developers to keep such life support running.
Since noone could be bothered with updating our port since at least 2016,
I doubt there's much interest.
packit is a mixture of tcpdump(1) and scapy(1), it's synopsis uses every
letter (upper and lower) of the alphabet and IPv6 is not supported at all
(not even printing captured packets).
Basic tests showed no output when capturing on lo(4) devices.
tl;dr: There's little to no value in beating a dead horse.
OK solene
