FS#53115 - [wireguard-tools] Make WIREGUARD-MODULE optional
Attached to Project:
Community Packages
Opened by Peter Wu (Lekensteyn) - Tuesday, 28 February 2017, 18:41 GMT
Last edited by Christian Hesse (eworm) - Sunday, 30 December 2018, 22:15 GMT
Opened by Peter Wu (Lekensteyn) - Tuesday, 28 February 2017, 18:41 GMT
Last edited by Christian Hesse (eworm) - Sunday, 30 December 2018, 22:15 GMT
|
Details
Description:
wireguard-tools includes stuff that do not depend on wireguard-dkms (manpages, binaries). A kernel could also be compiled with wireguard included for example and then I only need the binaries. Please consider making WIREGUARD-MODULE optional |
This task depends upon
Closed by Christian Hesse (eworm)
Sunday, 30 December 2018, 22:15 GMT
Reason for closing: Fixed
Additional comments about closing: wireguard 0.0.20181218-2
Sunday, 30 December 2018, 22:15 GMT
Reason for closing: Fixed
Additional comments about closing: wireguard 0.0.20181218-2
Manpages are useless without binaries, but I suppose I see the point re: containers relying on the module from the host system. Still that doesn't seem like the common use case, which would then be broken.
Maybe it would be less burdensome in a container, if it could depend on a wireguard package that provided the compiled module but did not need dkms. It's pretty easy to generate binary packages by makedepending on the dkms package: https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/broadcom-wl
Alternatively, maybe it would make sense for users of containers to install dummy packages that provide the things they know their host system has support for...