https://bugzilla.redhat.com/show_bug.cgi?id=1759940
--- Comment #11 from John Marshall <[email protected]> --- HTSlib uses the usual configure/make/make install build system, and falls back to a basic configuration if you didn't run configure. So your spec file should use configure, via %configure as appropriate. In particular Fedora should provide a fully-featured HTSlib build by configuring with ./configure --enable-plugins --with-plugin-path='/usr/local/libexec/htslib:$(plugindir)' --enable-libcurl --enable-gcs --enable-s3 See HTSlib's INSTALL file for details. This will activate HTSlib's plugin mechanism so that the Fedora-supplied libhts.so will be able to use any other file access plugins that the user may have installed, and will make Fedora's libhts.so use libcurl (thus variously incurring dependencies on libcurl and libcurl-devel) to enable HTTPS and related file access methods. Your current build can do basic FTP and HTTP but not HTTPS, which means it is of rapidly decreasing usefulness. The file format man pages (sam.5 etc) are aimed at users of tools eg samtools, not only at developers using the API. So IMHO they would fit better in the htslib-tools subpackage alongside the other manual pages. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
