[Debian-med-packaging] Bug#971542: Please enable HTSlib plugins

[Andreas Tille]

Control: tags -1 pending

On Thu, Oct 01, 2020 at 02:15:48PM +0000, John Marshall wrote:
> 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)'

Please inspect

   https://salsa.debian.org/med-team/htslib/-/commit/88644ba8e4096302d996dae2a0399195e2e53819

(and also your hint to the pull request
   https://salsa.debian.org/med-team/htslib/-/commit/84fcfcfda2b0b89d743bc8adb617abdf5cc22d4b )

> 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.

I guess you mean that I need to make sure that
    plugindir=/usr/lib/htslib
right?  It is sensible to assume that this is granted
by the fact that the library itself is installed under
/usr/lib ?  How can I verify / test the correct setting?

Kind regards

       Andreas.

-- 
http://fam-tille.de