[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Identifying legacy packages
Can we start clearly labelling why legacy packages are being kept
in their DESCR or by some other mechanism?
graphics/opencv2 - ??? nothing depends on this
graphics/MesaLib7 - Legacy platform support?
multimedia/libmp4v2 - KDE4 ... probably?
www/firefox52 - Last version without rust dependency
chat/inspircd - Still supported, chat/inspircd3 is semi-incompatible
In general, this helps out developers 10 years down the line who are
staring at these duplicates of up-to-date packages and wondering why
they exist, and prevents mistakes when including buildlinks.
Main Index |
Thread Index |