library name conflicts with regular Linux packages #430
Comments
|
Perhaps we should rename all the shared libraries provided by zfs to minimize the chance of a conflict. As previously noted The Currently the zfs package provides the following required libraries. As you suggest we could ensure they all start with libz , hopefully people won't confuse them with zlib's libz.a.
|
|
I recommend these changes to avoid current conflicts:
These two are iffy and could cause problems later:
That list of changes leaves libuutil and libzpool intact. Alternatively, everything for Linux could be recomposed into just libnvpair and libzfs, like on BSD and Solaris. Doing this would ensure that the linkages and autotools routines are consistent between Linux, kFreeBSD, OpenIndiana, et al. |
|
I'm not a huge fan of the libz prefix. Recomposing all the libraries in to a single libzfs to avoid conflicts seems like the cleanest thing to do. This includes libnvpair unless you have a good case for leaving it separate? I'm not going to have time to work on this any time soon. But I would like to see this done before tagging a stable 0.6.0 release. Darik would you have time to work on this? It looks like the right thing to do will just be to update the Makefiles to build everything as a convenience library and them merge them at the top level as described here: http://www.gnu.org/s/hello/manual/automake/Libtool-Convenience-Libraries.html |
These libraries, which are an artifact of the ZoL development process, conflict with packages that are already in distribution: * libspl: SPL Programming Language * libavl: AVL for Linux * libefi: GRUB And these libraries are potential conflicts: * libshare: the Linux Mount Manager * libunicode: Perl and Python Recompose these five ZoL components into the four libraries that are conventionally provided by Solaris and FreeBSD systems: + libnvpair + libuutil + libzpool + libzfs This change resolves the name conflict, makes ZoL more compatible with existing software that uses autotools to detect ZFS, and allows pkg-zfs to better reflect the official Debian kFreeBSD packaging. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes: #430
|
Closed by 7505628. Maybe Github doesn't automatically act on the commit "Closes:" line if it comes after an attribution line. |
…fs#430) `zcache hits` prints the number of cache hits, and the percent of lookups that are hits. However, the value printed is not accurate - it includes “ghost” hits, which do not actually return data to the caller, they just found an entry in the index for a recently evicted block. Notably, in the graph there are never any `*`'s after the `|`, incorrectly indicating that the cache size is double what it actually is, and that that increasing the cache size will not increase the hit rate. This commit corrects the problem by having the agent tell the `zcache` command how many actual (real, live) hits there were. Additional improvements: The `--quantiles` / `-q` option now specifies the total number of quantiles to display, instead of the number of quantiles of "live" data. Display start and end time in the local timezone Display elapsed time between start and end Set histogram width and length (quantiles) based on terminal size (or default to 80x24 if output is not a tty) Display hit percent with one decimal place Code cleanup, e.g. renaming variables
The
libavl.sofile provided by the ZFS utilities conflicts with the libavl-dev package that is already in Debian and Ubuntu:In pkg-zfs, this causes a package conflict that requires a lint override and a downstream package rename.
Consider renaming libavl to libzavl 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: