Ilya Lipnitskiy kirjoitti 18.2.2021 klo 19.48:
Hi,
On Thu, Feb 18, 2021 at 9:21 AM Adrian Schmutzler
<m...@adrianschmutzler.de> wrote:
I don't really get the point of this justification. Either wireguard-tools depends on
kmod-wireguard, or it doesn't. In the first case, and only then, it should be
"fixed" (with a proper justification describing that).
Are wireguard-tools useful without the underlying kernel module? It
didn't seem like it to me, although maybe Jason should chime in here,
as maintainer and developer of Wireguard.
As historical reference, please see the discussion in LuCI PR #855 in 2016,
when that aspect was discussed:
https://github.com/openwrt/luci/issues/855
The idea is to enable in-tree wireguard kernel modules on Linux 5.10
with a plan to phase out the out-of-tree module when 5.4 is taken out.
Reducing cross-repository dependencies makes it easier to accomplish.
It can be cumbersome to make a user-space package depend on alternative
kernel package variants depending on the kernel version, as we have some
package targets where the user-space package build SDK kernel version might
differ from the target SDK kernel. There were major difficulties with SQM &
cake a year ago.
See https://github.com/openwrt/packages/issues/12072
There the solution was an additional virtual kernel package, which could then
handle the kernel mainline / oot dependency difference inside the target.
https://github.com/openwrt/openwrt/pull/3039
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
