Date: Sun, 27 Dec 2020 15:09:33 +0100 From: "Kristof Provost" <kp@FreeBSD.org> To: "Baptiste Daroussin" <bapt@FreeBSD.org> Cc: freebsd-arch@freebsd.org Subject: Re: libifconfig non-private in 13? Message-ID: <E2B676D4-F9D0-41C9-B2FB-728607D70CFD@FreeBSD.org> In-Reply-To: <20201226211810.g4ll4ow23fitmxdo@ivaldir.net> References: <1EB6D7ED-F370-42EA-AC66-93D8BC96F29C@FreeBSD.org> <20201226211810.g4ll4ow23fitmxdo@ivaldir.net>
index | next in thread | previous in thread | raw e-mail
On 26 Dec 2020, at 22:18, Baptiste Daroussin wrote: > On Mon, Dec 21, 2020 at 09:02:00PM +0100, Kristof Provost wrote: >> Hi, >> >> Libifconfig was marked as private (and experimental) back in 2016. >> It’s since made some strides and has grown a few users. Ifconfig >> now depends >> on it as well. >> >> While it’s far from finished it’d be more useful for some users >> if it were >> public. That would at least imply some level of API/ABI stability, >> which is >> why I’m bringing it up here before pulling the trigger. >> >> Does anyone see any reasons to not do this? >> > > I would go the otherway around, any reason to make it public yet? if > yes they go > ahead, if no keep it private ;) > Well, I did ask because there’s at least one potential user asking for it. Best regards, Kristofhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E2B676D4-F9D0-41C9-B2FB-728607D70CFD>