Re: Re-importing WireGuard driver and utilities
- In reply to: John Baldwin : "Re: Re-importing WireGuard driver and utilities"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 01 Nov 2022 08:19:08 UTC
On Mon, 31 Oct 2022 at 18:02, John Baldwin <jhb@freebsd.org> wrote: > On 10/30/22 1:02 PM, Evilham wrote: > > Hey, > > > > On dj., oct. 13 2022, John Baldwin wrote: > > > >> Over the past several months, I have spent some time reviewing > >> the > >> WireGuard driver including its interactions with the rest of the > >> kernel and its use of crypto in the kernel. This work was > >> sponsored > >> by the FreeBSD Foundation and had a few goals: > > > > Thanks for all the work, I noticed something that might be related > > to how these changes interact with pkgbase: > > > > On pkg upgrade: > > > > - FreeBSD-runtime-dev-14.snap20221029192512 [evilham-base] > > conflicts with FreeBSD-runtime-14.snap20221029192512 > > [evilham-base] on /usr/include/dev/wg/if_wg.h > > > > Aka: the if_wg.h headers are included on both packages, how is > > this fixed? :-D would love to learn that. > > I have no idea. I can't figure out how it ended up in runtime-dev > reading include/Makefile which has a default PACKAGES of runtime. > Include files for PACKAGE=foo end up in a sibling package foo-dev. Not sure exactly where this happens - bsd.incs.mk is confusing me.