[Bug 250700] drm-kmod i915kms binary package not working on 12.2-RELEASE
Niclas Zeising
zeising at freebsd.org
Mon Dec 14 10:43:40 UTC 2020
On 2020-12-13 18:32, Miguel C wrote:
> This was indeed known and happened from 12.0 to 12.1 too, but I must admit
> it's kinda surprising nothing was done about it this time, isn't this just
> fixed by providing a 12.2 built package?
>
> I was curious too why that was not done, but since building it doesn't
> take long I was OK with it, but it would be nice to see this address in
> future, I'm guessing it will be the same for 13 and so on right?
>
> Or is there a better solution to having multiple port flavors?
The problem is far from simple to fix.
The issue is that FreeBSD packages are built on the lowest common
denominator, which menas that packages for FreeBSD 12.1 and 12.2 are
built on FreeBSD 12.1, and will be done that way until FreeBSD 12.1 is EOL.
Currently, there is no good way or good support for building a specific
package (or set of packages) on another version of FreeBSD and have
those be preferred, at least that's my understanding
Just creating a different package, say drm-fbsd12.2-kmod, won't work,
since that will still be built on FreeBSD 12.1 (or not built at all, if
we restrict it to only building on FreeBSD 12.2 or later). Having a
different package name also means that people upgrading from 12.1 to
12.2 won't get the new package without manual intervention.
For FreeBSD 13.0 this won't be a problem, since packages for FreeBSD
13.0 are built on FreeBSD 13.0.
Regards
--
Niclas Zeising
More information about the freebsd-x11
mailing list