My attempt at an #OpenZFS "libzfs" in /usr/include/openzfs PR for #FreeBSD:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289655
Your wisdom please!
Discussion
Loading...
Post
@dexter I stand by my comments in here: https://lobste.rs/s/56ys0f/we_should_improve_libzfs_somewhat#c_qanicz
libzfs is not something people should be building against at all
@jmc @dexter I've had that comment in a tab for months, because I really want to reply to it properly. some I agree with, some I don't, some I'm still chewing on. someday I'll get there I swear
we do at least agree on "don't use libzfs". the trouble is that I don't really have anything better to offer people who want or need something beyond the cli tools. and that really the point of the post: survey the field, describe the current state of things, and ponder what we might do instead
@dexter Last time I tried to use libzfs, the issue was not that the headers were missing (I could add the ones in the src tree without too much difficulty) it was that they were incompatible with base-system headers. They needed special Solaris definitions of things and the headers that provided them were incompatible with other base system headers. Actually including the libzfs headers broke includes of anything else. The builds of libzfs and zfs live in their own little Solaris-flavoured world, trying to use libzfs with anything else was impossible.
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled