Re: git: 028382670670 - main - usr.bin: hook wg(8) up to the build
- In reply to: Kyle Evans : "Re: git: 028382670670 - main - usr.bin: hook wg(8) up to the build"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 31 Oct 2022 03:39:16 UTC
In message <CACNAnaHJPARmYVmyaJZMQfEXZYeGZfWpJ+hc7ETEmRkXXxALaw@mail.gmail.c om> , Kyle Evans writes: > On Sun, Oct 30, 2022 at 8:22 AM Florian Smeets <firstname.lastname@example.org> wrote: > > > > On 29.10.22 05:10, Kyle Evans wrote: > > > The branch main has been updated by kevans: > > > > > > URL: https://cgit.FreeBSD.org/src/commit/?id=0283826706706c598fff86e16c42 > 604841c1a05a > > > > > > commit 0283826706706c598fff86e16c42604841c1a05a > > > Author: Kyle Evans <kevans@FreeBSD.org> > > > AuthorDate: 2022-10-29 03:04:56 +0000 > > > Commit: Kyle Evans <kevans@FreeBSD.org> > > > CommitDate: 2022-10-29 03:05:39 +0000 > > > > > > usr.bin: hook wg(8) up to the build > > > > > > wg(8) is used to manage WireGuard interfaces; see wg(4) and wg(8) bo > th > > > for more details and usage examples. > > I just migrated from the ports version to the in tree version, the only > > thing missing seems to be the rc script, other than that it's working fine. > > > > Should we import an rc script into base e.g. one the net/wireguard-tools > > provides? > > > > I wouldn't mind one, though we can't really provide the one the > wireguard-tools provides; it's based entirely off of wg-quick(8), > which we can't reasonably install in base (bash script and actually > uses bash-isms). I think our options are limited. Either import ksh from https://github.com/ksh93/ksh, resurrected ksh development, if the EPL 2.0 license is to our liking or try to simulate arrays, like we do in rc. I think the latter risks introducing bugs, not to mention cumbersome, while the former is very actively developed. Personally, I think we might want to revisit importation of the actively developed ksh (above), if not for public consumption (i.e. /bin/ksh), for support of arrays (as /usr/libexec/ksh). Many of the additional ksh features are POSIX as well. I think the last time we looked at anything ksh-like, it was for its interactive use. I think we should consider it for its scripting capabilities (as in /usr/libexec/ksh) only and let users choose interactive options from ports. -- Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: https://FreeBSD.org NTP: <email@example.com> Web: https://nwtime.org e^(i*pi)+1=0