Source: htslib
Version: 1.11-1
I would recommend building HTSlib with plugins enabled. Doing this will
activate HTSlib's plugin mechanism so that the Debian-supplied libhts.so will
be able to use any other file access plugins that the user may have installed,
and will move e.g. the libcurl and associated library dependencies to
hfile_libcurl.so (which libhts.so will dynamically load) which simplifies
linking against libhts.a for other programs. This can be done by adding the
following configure options:
./configure --enable-plugins
--with-plugin-path='/usr/local/libexec/htslib:$(plugindir)'
See HTSlib's INSTALL file for details. Packagers such as yourselves should set
with-plugin-path thus so that plugins in both /usr/local and /usr will be used;
If Debian still folds /usr/libexec into /usr/lib or nearby, you may wish to
adjust both --with-plugin-dir and --with-plugin-path.
Thanks,
John
