From owner-freebsd-arch@freebsd.org Mon Dec 21 20:02:02 2020 Return-Path: Delivered-To: freebsd-arch@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 139814C30A2 for ; Mon, 21 Dec 2020 20:02:02 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D09NV09PZz4VGS for ; Mon, 21 Dec 2020 20:02:02 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from venus.codepro.be (venus.codepro.be [5.9.86.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.codepro.be", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: kp) by smtp.freebsd.org (Postfix) with ESMTPSA id D840236A8 for ; Mon, 21 Dec 2020 20:02:01 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: by venus.codepro.be (Postfix, authenticated sender kp) id B2AA3412FD; Mon, 21 Dec 2020 21:02:00 +0100 (CET) From: "Kristof Provost" To: freebsd-arch@freebsd.org Subject: libifconfig non-private in 13? Date: Mon, 21 Dec 2020 21:02:00 +0100 X-Mailer: MailMate (1.13.2r5673) Message-ID: <1EB6D7ED-F370-42EA-AC66-93D8BC96F29C@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2020 20:02:02 -0000 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? Regards, Kristof