Date: Thu, 09 Sep 2021 04:39:42 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 193748] Userland support for libzfs and libzfs_core feature request Message-ID: <bug-193748-3630-SEsKRZQklC@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-193748-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-193748-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193748 Alan Somers <asomers@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed CC| |asomers@FreeBSD.org Resolution|--- |FIXED --- Comment #3 from Alan Somers <asomers@FreeBSD.org> --- The thing about libzfs is that it is not a stable interface. It was never intended to be one, and never has been. It changes frequently, and in non-backwards compatible ways. That's why its use is highly discouraged by programs outside of the base system. The few that do use it (sysutils/py-iocage for example) typically break during an OS upgrade. libzfs_core, OTOH, _is_ a stable interface. It has a simple API, very simi= lar to what the zfs command line tools provide. And it's guaranteed to preserve backwards compatibility. FreeBSD 13+ include libzfs_core.h in /usr/include, and libzfs_core is final= ly mature enough that you can write useful applications with it. So I think t= his bug is finally resolved. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193748-3630-SEsKRZQklC>