Feedstock license: BSD-3-Clause
Home: http://tiledb.com
Package license: MIT
Summary: Efficient variant-call data storage and retrieval library using the TileDB storage library.
Development: https://github.com/TileDB-Inc/TileDB-VCF
Documentation: https://docs.tiledb.com/developer/tiledbvcf/introduction
TileDB-VCF is the python interface to the TileDB-VCF library.
Azure |
Name | Downloads | Version | Platforms |
---|---|---|---|
Installing tiledb-vcf
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, libtiledbvcf, tiledbvcf-py
can be installed with conda
:
conda install libtiledbvcf tiledbvcf-py
or with mamba
:
mamba install libtiledbvcf tiledbvcf-py
It is possible to list all of the versions of libtiledbvcf
available on your platform with conda
:
conda search libtiledbvcf --channel tiledb
or with mamba
:
mamba search libtiledbvcf --channel tiledb
Alternatively, mamba repoquery
may provide more information:
# Search all versions available on your platform:
mamba repoquery search libtiledbvcf --channel tiledb
# List packages depending on `libtiledbvcf`:
mamba repoquery whoneeds libtiledbvcf --channel tiledb
# List dependencies of `libtiledbvcf`:
mamba repoquery depends libtiledbvcf --channel tiledb
If you would like to improve the tiledb-vcf 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/tiledb-vcf-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.