Date: Mon, 31 Oct 2022 11:02:18 -0700 From: John Baldwin <jhb@FreeBSD.org> To: Evilham <contact@evilham.com> Cc: freebsd-arch@freebsd.org Subject: Re: Re-importing WireGuard driver and utilities Message-ID: <81989eb2-75e2-b779-0c4b-99cd07d99218@FreeBSD.org> In-Reply-To: <c12124a2567275a47d92243c8bc62193effd@yggdrasil.evilham.com> References: <742c4fe8-4c25-d7e5-1df3-b2851d90e630@FreeBSD.org> <c12124a2567275a47d92243c8bc62193effd@yggdrasil.evilham.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?81989eb2-75e2-b779-0c4b-99cd07d99218>