Re: nvidia-driver and no update in /usr/ports/UPDATING

On Fri, Apr 08, 2022 at 04:28:16AM +0100, Steve O'Hara-Smith wrote:
>	No I think you should help by making actionable bug reports and
>understanding that when something doesn't happen the best response is to
>help make it happen not complain about it and that phrases like "*WHY* the
>*F**K* isn't in *UPDATING??!??!?!?!*" are unhelpful ranting so *WHY* the
>*F**K* didn't YOU provide some TEXT and cc the MAINTAINER in your
>bug report??!??!?!?! there's a FSCKING STANDARD for good bug reports D*MN
>WELL FOLLOW IT* - see how does it feel ?

Feels fine to me and has a bit of useful information. I am not joking.

Like I said, back then I thought it was sufficient to just submit 
the bug

> phrases like "*WHY* the *F**K* isn't in *UPDATING??!??!?!?!*"

wasn't in the bug report I cited (for the font)

Anyway, nvidia-driver not being in UPDATING is this really a bug?

I would have not posted my original missive here if there was somewhere 
better to write. I know from the other bug cited it was unlikely to be 
actioned, or acknowledged. I don't know what else to do, apart from 
use something else, which I really don't want as i've been using 
freebsd since 1997.

The situation as it is right now, is untenable. I can't support end users 
depending on ports that change executable names and locations 
and other properties without notice. This is like the 10th time something
like this has happened where it's been major.
-- 
J.