libifconfig non-private in 13?
Li-Wen Hsu
lwhsu at freebsd.org
Sat Dec 26 21:33:37 UTC 2020
On Sun, Dec 27, 2020 at 5:18 AM Baptiste Daroussin <bapt at freebsd.org> 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 ;)
I would say it is nice to have some scripting language bindings to it,
although I'm not sure if this is possible and a feasible usage.
Best,
Li-Wen
More information about the freebsd-arch
mailing list