Skip to content

Could SeqLib and htslib work out what a public cram api should be? #21

@detrout

Description

@detrout

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions