Skip to content

TileDB-Inc/htslib-feedstock

Repository files navigation

About htslib-feedstock

Feedstock license: BSD-3-Clause

Home: https://github.com/samtools/htslib

Package license: MIT

Summary: C library for high-throughput sequencing data formats.

Documentation: http://www.htslib.org/

Current build status

Azure
VariantStatus
linux_64_libdeflate1.17 variant
linux_64_libdeflate1.21 variant
osx_64 variant
osx_arm64 variant

Current release info

Name Downloads Version Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms

Installing htslib

Installing htslib from the tiledb channel can be achieved by adding tiledb to your channels with:

conda config --add channels tiledb
conda config --set channel_priority strict

Once the tiledb channel has been enabled, htslib can be installed with conda:

conda install htslib

or with mamba:

mamba install htslib

It is possible to list all of the versions of htslib available on your platform with conda:

conda search htslib --channel tiledb

or with mamba:

mamba search htslib --channel tiledb

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search htslib --channel tiledb

# List packages depending on `htslib`:
mamba repoquery whoneeds htslib --channel tiledb

# List dependencies of `htslib`:
mamba repoquery depends htslib --channel tiledb

Updating htslib-feedstock

If you would like to improve the htslib recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the tiledb channel, whereupon the built conda packages will be available for everybody to install and use from the tiledb channel. Note that all branches in the TileDB-Inc/htslib-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

  • If the version of a package is not being increased, please add or increase the build/number.
  • If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages