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

Package license: GPL

Feedstock license: BSD-3-Clause

Summary: BCFtools is a set of utilities that manipulate variant calls in the Variant Call Format (VCF) and its binary counterpart BCF. All commands work transparently with both VCFs and BCFs, both uncompressed and BGZF-compressed. Most commands accept VCF, bgzipped VCF and BCF with filetype detected automatically even when streaming from a pipe. Indexed VCF and BCF will work in all situations. Un-indexed VCF and BCF and streams will work in most, but not all situations.

Azure

Variant Status linux_64 osx_64 win_64

Name	Downloads	Version	Platforms

Installing bcftools 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, bcftools can be installed with conda:

conda install bcftools

or with mamba:

mamba install bcftools

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

conda search bcftools --channel tiledb

or with mamba:

mamba search bcftools --channel tiledb

Alternatively, mamba repoquery may provide more information:

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

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

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

If you would like to improve the bcftools 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/bcftools-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.