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.
security support it appears this is not really the case any more
https://bugs.php.net/bug.php?id=81026
add @pkgpaths to merge pecl-* etc across
mark www/syweb broken, it was marked 7.3-only so looks like it needs more work
other php-ish ports have a RDEP on either 7.4 (default version) or 8.0
worth fixing (it's a netstumbler-like toolset for wi(4) - a FreeBSD
forum post from 2009 said "bsd-airtools is dead", and at that point they
already had a newer version than in OpenBSD ports).
Fails to build with "-fno-common" and busy loop stat(2)s watched files
driving up CPU usage instead of using kevent(2) or so.
No activity upstream, FreeBSD maintains a port with local patches called
(security/l0pht-watch in their ports tree) in case anyone is interested
in resurrecting this.
OK jca naddy
Upstream still ships the tarball, that's it, as per CVS log:
"primary distsite and homepage have gone away".
The only TCP port I've been able to detect (after producing traffing on a
variety of them) is SSH -- and that only worked after enabling IPv4.
Siphon does not seem to support/detect IPv6 at all and it's OS fingerprints
are extremely old; besides Gentoo we're the only ones still packaging it
according to https://repology.org/project/siphon/versions .
Fails with "-fno-common".
OK cwen
That's a NetBus 1.6 client... upstream's dead as in NXDOMAIN, we seem to be
the only folks still packaging it.
It has not changed in twenty years (surprise!) and basically only exists to
screw around with old old Windows boxes which... still run the server?
Fails with "-fno-common".
OK jsg
Over half a year ago I dropped MAINTAINER on this port due to not using it
any longer. At that time it was already outdated. Noone spoke up to
update or even maintain it.
The new (unported) version 1.6.0 already suffers from TLS related build
failures, now there's another problem: it does not build with "-fcommon"
which will become a default compiler option in the tree.
If someone wants to fix both and get an up-to-date version running they
recover it from the attic.
OK tb
letsencrypt have already stopped allowing ACMEv1 for new domain
validations, and are now doing "brownouts" for all ACMEv1 access,
disabling it temporarily twice a month for increasing lengths of
time (6/24/48/72/120/168 hours) in the run up to disabling it
completely on June 1st.
