Recent ports removal

[Xin LI]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

(I just picked one message to do a reply-all, not specific to any one
single message but all of them).

Technically speaking the current approach's problem is that the user
might have no chance of seeing it before the port is removed.  By its
nature, deprecated ports tends not to be updated for long time, port
tools like portmaster, portupgrade will not even see it because no
PORTREVISION bump happen.  For users who install from packages, there
is no deprecation message at all, and it's pretty likely that these
user when updating to a new version suddenly find the software missing.

I think if we want to deprecate ports in a constant manner, we need to
do a better job of letting the user (or let's say potential
contributor) know it.  My own server in China have went offline for a
few months before my friend rebuild and install one for me, and I
suddenly noticed that some of previous ports maintained by someone
else have been marked as DEPRECATED because upstream gone.

Think about this: FreeBSD is not just a product, it's also a project
and a community.  It's never an overkill to do more things to keep
developers, contributors and potential contributors happy and continue
to contribute.  Making them happy is not "do whatever they want us to
do" but to think more about "what they would think, and how we can
improve".

Cheers,
- -- 
Xin LI <delphij at delphij.net>	https://www.delphij.net/
FreeBSD - The Power to Serve!		Live free or die
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)

iQEcBAEBCAAGBQJOvZ5uAAoJEATO+BI/yjfBkxYIAKwfR3KRGr4l0AY1fV8Os0MR
+0GTUlOnTtaIybk81NcmLhyonSr1GsKAbqyAz5D9hsVFWdNOIeP6G/AnYRIak9Gs
ffrFCIN6WjiFmYORQVSTOl3noQmAC4E066vl2PceOUL8sHyHI6O85SuraY0noaVQ
p3AV58sQqIuUTpV4f3gPG1nFiDrJT1ZxtLANWjveSNNKDrdcalgjPtPbv1DUYPgp
10me7cVkqp5rrCs2fVUP92037x7XljAZjDi8AaEPf/LtV7Rb+IgC9bE1erk8u8w5
RHoWp2er6szTi70v3CUH7YI7WV31wpphBCY75w/kcvJ4FW1OmUOMjXksVfvLZo8=
=xhBR
-----END PGP SIGNATURE-----