I’m trying to package an out-of-tree driver as an akmod. The idea is that users will be able to layer it with rpm-ostree, and akmods will take care of rebuilding and signing whenever the kernel is updated. To my understanding, akmods depends on a matching kernel-devel installed on the system to do its magic, and the package offered in Fedora repos is newer than what we have. I was able to download the correct rpm off build archives but it’s a non-starter for distribution for obvious reasons. Any ideas on how to get around this (save for manually building the module for each kernel update)? Am a complete noob when it comes to akmods, sorry😅
We build our akmods packages in GitHub. Then copy the rpms to a scratch container and upload to a registry.
See GitHub - ublue-os/akmods: A caching layer for pre-built Fedora akmod RPMs
Okay I checked the following:
- module builds and installs on copr and in a fedora 41 VM with akmods
- module builds manually, signs, loads, and works on aurora:stable
Anything else I need to test before this is ready for a PR?