zirias@
Developer
I just spat some random thoughts about how "doing it right" might look like ... mainly to make the point that's a pretty complex thing and just not worth the effort for very few affected packages
I just spat some random thoughts about how "doing it right" might look like ... mainly to make the point that's a pretty complex thing and just not worth the effort for very few affected packages
It's a small port/package, it should be done quite quickly even on modest hardware. High speed fan is good, your CPU is probably at 100% usage, which is a good thing to happen when compiling. I wonder what's it's been doing the past 5 hours though. Just ctrl-C it to break it off. It's probably trying to build way too much other things (bunch of build dependencies maybe?).
Please show exactly what you did. My guess: either you built something else,
According to FreshPorts it depends on devel/kBuild, which depends (always for building) on:
pkg install this before building. It mislead me because none of these dependencies should ever be necessary for native FreeBSD kernel modules. But I guess the virtualbox kmod isn't exactly "native" FreeBSD code ?
pkg install -A gmake texinfo gcc12 automake autoconf binutils kBuild beforehand. You could also use make install-missing-packages but one of the build dependencies will cause it to spiral somewhat out of control and pull in a gazillion unneeded packages. Recommend adding the -A option to pkg-install(8) so these packages are all registered as "automatic". This makes it easy to remove them with pkg-autoremove(8) when you're done.
Probably, but it won't hurt to explicitly install them, especially with the added
-A flag.Just update your ports collection
portsnap fetch update.
pkg install the build dependencies) and did make reinstall of emulators/virtualbox-ose-kmod with ports. And yes, I updated the ports before.If I lock the package it will not get updates, I mean, I'm believing that the next version will be compiled for version 13.2.
Depends. Until 13.1 won't be EOL, if there will be updates for a package, they'll be compiled for it.
How hard would it be for pkg to check this OS version dependency and print out a message (in case the host version is different than the one expected)? Ideally with a one liner the user can cut-n-paste to build from ports. Of course, this would likely need adding yet another thing to the port system that pkg can rely on.
13.2 was released yesterday (11 April), so until 11 July 13.1 will still be the default one for pkgs builds. However, Virtualbox (according to its commit history) doesn't get updates too often, just every ~3 month. You shuold be fine for the time being.
It does, it complains if the packaged OS version is newer than what you have installed.
Is a comeback of drm-kmod in base actually planned/wanted by the developers? I thought it was moved to ports so that support for newer graphics hardware could be made available without users having to wait for the next stable release, which is a positive change. On the other hand, it's true that these three months of incompatibility are a bit annoying, sometimes you'd prefer not to need the ports collection and be able to rely on packages only (some people will even label as heresy any local build from ports on a system using packages...), in this case you're forced to stick with the previous release until its very end of life.
