This is why all we need to move to federated Gitea/foregjo asap /s
This is why all we need to move to federated Gitea/foregjo asap /s
"/s" is known as the sarcasm switchGot it.
about the automation before the fancy featuresmfw the automation is the fancy feature

akmods instead?", because akmods is just a wrapper around akmodsbuild which attempts to build and then INSTALL the RPMs which won't work on rpm-ostree. So do cat "$(which akmods)" | grep akmodsbuild -C10 to read how akmods runs the build tool, and then install the RPMs manually with rpm-ostree install.But akmods is the easy way.Tbh, comparing what I did in my build, vs say what bsherman did for his build I'm not convinced either way is that much easier or harder than the other - at least for the case of xone (perhaps some other project would be more than a oneliner to build)Leverage if you can.
The solution you posted was pulling driver files from another image which is fragile.To be clear about what my way is doing, it is a single Containerfile which uses multi stage build. First there's a
driver stage that builds the kernel modules - straight from the upstream source code. This stage is based on ublue main. Then later I install the resulting artifacts into the actual output stage image - this is also based on ublue main and hence should have exactly the same kernel (except perhaps if there's some way for things to have changed during the run, but that would be a solvable problem and as I mentioned this was mostly a proof of concept).make