Date: Mon, 13 Apr 2020 21:23:28 -0400 From: Theron <theron.tarigo@gmail.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: Niclas Zeising <zeising@freebsd.org>, Grzegorz Junka <list1@gjunka.com>, "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org>, emaste@freebsd.org Subject: Re: Ars Technica article Message-ID: <9376cd2c-893b-bf9f-ea45-f4805dc74947@gmail.com> In-Reply-To: <CAN6yY1sXNy%2BJLpsqcqzJafUd-%2B_UfU1FJZQ88du_3D29wwrznQ@mail.gmail.com> References: <4e3bf6be-aecf-7c62-df98-1cc4b01b8db9@gmail.com> <qjPID4gTE2NvAVjSZKmSBSLDOK7gxaJbnPw46O71vKnmV0b7uoMZ7xTv3RI30bRpPqphZAXTHd3r3RYSQ8UGaRVO45afo-EcYB34INKVAM8=@protonmail.ch> <43f83193-e495-2bf2-f85d-91aa0b36c1a0@gmail.com> <slUQwwm1giIIEaqmUKBQ1G5UIlVSvzfWkk3vZm-dBYNRA-wng7tDluv_Es3eOiaNYDE9yNtKFfd-2iOEozSGK1JNIjFbqCXV1a1sgkQ1sHE=@protonmail.ch> <0e205fe8-fbc6-5d91-99b0-1bd4870b8a5d@gmail.com> <CAGwOe2ZHZFhVwSvjk7JDe0szY-1oZH_HvDhMqp-zXXV9%2BePtHg@mail.gmail.com> <d263368c-5dcc-61c2-9c77-3d59c5493182@gmail.com> <536A0D50-4119-4C28-9202-28622152B203@freebsd.org> <20200413052406.GA90880@FreeBSD.org> <CANCZdfqfkVGDGssHC%2Bts6df7QeiCsA68CQnjOAAXdH2JsDMTaQ@mail.gmail.com> <20200413075034.GA46382@FreeBSD.org> <2761dfd9-f031-9a47-024e-71ef29f9ac23@gjunka.com> <e0d5490b-4d6b-bf4a-1e53-15574a373842@freebsd.org> <24943162-97e4-7221-45c8-aeda7907c168@gmail.com> <CAN6yY1sXNy%2BJLpsqcqzJafUd-%2B_UfU1FJZQ88du_3D29wwrznQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9376cd2c-893b-bf9f-ea45-f4805dc74947>