Ars Technica article

[Theron]

On 2020-04-13 21:01, Kevin Oberman wrote:
> It is, of course, drm-fbsd12.0-kmod is actually the port.
I did mean to refer to drm-fbsd12.0-kmod, not the meta-port, but I 
wasn't clear.

> This problem has hit both drm-fbsd12.0-kmod and virtualbox-ose-kmod in 
> the past and has caused real pain that would have avoided by simply 
> building a trusted port for these kmod ports whenever a RELEASE is made.
I'm not sure what you have in mind.  12.x installations share a single 
pkg repository, although Ed Maste has suggested (in the Github issue) 
using minor-release-specific repository overlays for kmod ports.  To me 
it sounds like the "right thing" but I'm not clear on the technical and 
maintenance obstacles.

> Of course, people running head or STABLE should be aware that they 
> should build these ports from source and not install a package.
Ideally so, and mostly it seems to be -RELEASE users complaining about 
the packages, however considering that kmod incompatibility is 
system-fatal while port userspace ABI breakage is usually not, an 
appropriate pkg-message might be appreciated.

Theron