Hello,
In investigating packaging issues with htslib on Debian, we discovered that SeqLib is using functions htslib considers private (anything in cram/*.h)
Debian modified htslib to allow linking to the cram functions in the normal shared library, but the htslib developers have told us to not do that. Normally you're using an embedded copy of htslib, and can directly access private functions.
In an ideal world htslib would actually have a supported public cram API.
Could you talk a bit with the htslib developers about what you'd actually need from them?
Hello,
In investigating packaging issues with htslib on Debian, we discovered that SeqLib is using functions htslib considers private (anything in cram/*.h)
Debian modified htslib to allow linking to the cram functions in the normal shared library, but the htslib developers have told us to not do that. Normally you're using an embedded copy of htslib, and can directly access private functions.
In an ideal world htslib would actually have a supported public cram API.
Could you talk a bit with the htslib developers about what you'd actually need from them?