You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2020. It is now read-only.
I hear what your saying, we really should resolve the library naming conflicts before tagging an official release. That said, I'm closing this bug and moving it over to the zfs issue tracker. The spl package only provides a spl.ko kernel module, libspl.{a.so} are provided by the zfs package.
Just talked with Brian about this regarding Lunar Linux; apart from the library issue, the naming of "spl" could be different as well (not sure if I should open a new issue for that, hence i write here) the name spl is already taken by the programming language, hence I named it "solaris-porting-layer" in lunar. We really shouldn't name this spl anymore (even if that might look simple at a first glance) because SPL could stand for a wide range of things... SPL in PHP, SPL the programming language.. etc, so either something long which explains it well (solaris-porting-layer) or zfs-spl (iirc only zfs is using it, isn't it?)
The
libspl.a
file provided by the Solaris Porting Layer conflicts with the spl-dev package that is already in Debian and Ubuntu:In pkg-spl, this causes a package conflict that requires a lint override.
Consider renaming libspl to libzspl so that it does not conflict with any other software that is already in regular distribution.
The text was updated successfully, but these errors were encountered: