I have recently installed nvidia-dkms as I use linux-hardened, although I have installed linux package as well, but I always boot to linux-hardened.
Anyway I've noticed that nvidia-dkms increases pkgrel everytime linux package gets upgraded, why is that so?
Taken from NVIDIA wiki:
Custom kernel
If you are using a custom kernel, compilation of the Nvidia kernel modules can be automated with DKMS.
Install the nvidia-dkms package (or a specific branch). The Nvidia module will be rebuilt after every Nvidia or kernel update thanks to the DKMS pacman hook.
Correct me if I'm wrong but it doesn't mean that nvidia module will be rebuilt after kernel update thanks to the DKMS pacman hook?
So why should nvidia-dkms upgrades?
On Tue, Mar 31, 2020 at 12:48 PM Amin Vakil info@aminvakil.com wrote:
So why should nvidia-dkms upgrades?
it's because nvidia-dkms is part of a split package that builds both nvidia and nvidia-dkms. The bump in pkgrel is to rebuild nvidia for the new kernel, and as a consequence the pkgrel for nvidia-dkms is bumped too, even though it is unnecessary.
-Chris
On 3/31/20 12:54 PM, Chris Billington via arch-general wrote:
On Tue, Mar 31, 2020 at 12:48 PM Amin Vakil info@aminvakil.com wrote:
So why should nvidia-dkms upgrades?
it's because nvidia-dkms is part of a split package that builds both nvidia and nvidia-dkms. The bump in pkgrel is to rebuild nvidia for the new kernel, and as a consequence the pkgrel for nvidia-dkms is bumped too, even though it is unnecessary.
See the broadcom-wl PKGBUILD for how to avoid this. Also note the wireguard-{arch,lts} packages have adopted this method.
It's up to Sven-Hendrik Haase if he wants to do this, though.
Em março 31, 2020 14:03 Eli Schwartz via arch-general escreveu:
See the broadcom-wl PKGBUILD for how to avoid this. Also note the wireguard-{arch,lts} packages have adopted this method.
It's up to Sven-Hendrik Haase if he wants to do this, though.
Well, the best way to avoid this is a complete separate package. But also increases the burden on the maintainer. So, it's up to Sven to do this, but I don't think it's strictly necessary.
Regards, Giancarlo Razzolini
On 3/31/20 1:31 PM, Giancarlo Razzolini wrote:
Em março 31, 2020 14:03 Eli Schwartz via arch-general escreveu:
See the broadcom-wl PKGBUILD for how to avoid this. Also note the wireguard-{arch,lts} packages have adopted this method.
It's up to Sven-Hendrik Haase if he wants to do this, though.
Well, the best way to avoid this is a complete separate package. But also increases the burden on the maintainer. So, it's up to Sven to do this, but I don't think it's strictly necessary.
I would argue it *reduces* the maintenance burden, since you can use the dkms package as a single source of truth, and makedepends on it to build. You already know the dkms version should build.
I've even templated it so it is trivial to do
pkgname="${pkgname}-customkernel" and have it do everything correctly to build for a different kernel.
arch-general@lists.archlinux.org