Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#69235 - [wireguard-dkms] Split into wireguard-src and wireguard-dkms
Attached to Project:
Arch Linux
Opened by Hussam Al-Tayeb (hussam) - Wednesday, 06 January 2021, 17:29 GMT
Last edited by Eli Schwartz (eschwartz) - Wednesday, 21 April 2021, 13:14 GMT
Opened by Hussam Al-Tayeb (hussam) - Wednesday, 06 January 2021, 17:29 GMT
Last edited by Eli Schwartz (eschwartz) - Wednesday, 21 April 2021, 13:14 GMT
|
DetailsThere is an unnecessary conflict between the source code and binary module here.
Basically currently, wireguard-dkms conflitcs with wireguard-lts for obvious reasons. This means that if I patched my kernel and I need to rebuild wireguard-lts, I have to install wireguard-dkms which tracks its own module installations in addition to triggering an unintentional build when my actual intention is the build dependency of wireguard-lts. Then if I want to install wireguard-lts, wireguard source code gets uninstalled since it is part of wireguard-dkms. This makes little sense since the source code should not conflict with the binary kernel module. This can be avoided by splitting into wireguard-src and wireguard-dkms. This avoids an unnecessary conflict between the source code and the binary kernel module. |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Wednesday, 21 April 2021, 13:14 GMT
Reason for closing: Not a bug
Additional comments about closing: The built binary modules are only intended for users who aren't building the module themselves, and are merely building it for distribution to others.
Like a distro repo distributes it to others.
If you need to locally rebuild the wireguard module you can just install wireguard-dkms on your production machine, no explanation for why this isn't feasible has been offered.
Wednesday, 21 April 2021, 13:14 GMT
Reason for closing: Not a bug
Additional comments about closing: The built binary modules are only intended for users who aren't building the module themselves, and are merely building it for distribution to others.
Like a distro repo distributes it to others.
If you need to locally rebuild the wireguard module you can just install wireguard-dkms on your production machine, no explanation for why this isn't feasible has been offered.
The problem with making a split package build both is that every time any of our various kernels gets updated, the module needs to be rebuilt, and we don't want to also rebuild the dkms package for no reason other than to rebuild the other half of the split package.
So if I install wireguard-dkms in the clean chroot, the dkms module will also get built. correct?
Anyway, it's a pacman hook -- personally I'd mask the dkms hook in build chroots to prevent that kind of rebuild.