Date: Tue, 1 Nov 2022 08:19:08 +0000 From: Doug Rabson <dfr@rabson.org> To: John Baldwin <jhb@freebsd.org> Cc: Evilham <contact@evilham.com>, freebsd-arch@freebsd.org Subject: Re: Re-importing WireGuard driver and utilities Message-ID: <CACA0VUja2eCV5syZ_sh7ALo08U_U8-xT7sZm=TqTg95X9HuFhw@mail.gmail.com> In-Reply-To: <81989eb2-75e2-b779-0c4b-99cd07d99218@FreeBSD.org> References: <742c4fe8-4c25-d7e5-1df3-b2851d90e630@FreeBSD.org> <c12124a2567275a47d92243c8bc62193effd@yggdrasil.evilham.com> <81989eb2-75e2-b779-0c4b-99cd07d99218@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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. [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 31 Oct 2022 at 18:02, John Baldwin <<a href="mailto:jhb@freebsd.org">jhb@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">On 10/30/22 1:02 PM, Evilham wrote:<br> > Hey,<br> > <br> > On dj., oct. 13 2022, John Baldwin wrote:<br> > <br> >> Over the past several months, I have spent some time reviewing<br> >> the<br> >> WireGuard driver including its interactions with the rest of the<br> >> kernel and its use of crypto in the kernel. This work was<br> >> sponsored<br> >> by the FreeBSD Foundation and had a few goals:<br> > <br> > Thanks for all the work, I noticed something that might be related<br> > to how these changes interact with pkgbase:<br> > <br> > On pkg upgrade:<br> > <br> > - FreeBSD-runtime-dev-14.snap20221029192512 [evilham-base]<br> > conflicts with FreeBSD-runtime-14.snap20221029192512<br> > [evilham-base] on /usr/include/dev/wg/if_wg.h<br> > <br> > Aka: the if_wg.h headers are included on both packages, how is<br> > this fixed? :-D would love to learn that.<br> <br> I have no idea. I can't figure out how it ended up in runtime-dev<br> reading include/Makefile which has a default PACKAGES of runtime.<br></blockquote><div><br></div><div>Include files for PACKAGE=foo end up in a sibling package foo-dev. Not sure exactly where this happens - <a href="http://bsd.incs.mk">bsd.incs.mk</a>; is confusing me.</div><div><br></div></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACA0VUja2eCV5syZ_sh7ALo08U_U8-xT7sZm=TqTg95X9HuFhw>