mesa libs issue

Walter Schwarzenfeld w.schwarzenfeld at utanet.at
Sun May 14 01:14:26 UTC 2017


and these all happens, cause a message in
/usr/ports/UPDATING is missing. I am sure nearly nobody reads 
/usr/ports/MOVED (cause
the most entries are no very interesting).
If such important changes are made, it needs
an entry in /usr/ports/UPDATING.


More information about the freebsd-ports mailing list