conda-forge / metawrap-feedstock

A conda-smithy repository for metawrap.

About metawrap

Home: http://github.com/jakirkham/metawrap

Package license: BSD 3-Clause

Feedstock license: BSD 3-Clause

Summary: A collection of wrappers for functions and classes.

Current build status

All platforms:

Current release info

Name	Downloads	Version	Platforms

Installing metawrap

Installing metawrap from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge

Once the conda-forge channel has been enabled, metawrap can be installed with:

conda install metawrap

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

conda search metawrap --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by CircleCI, AppVeyor and TravisCI it is possible to build and upload installable packages to the conda-forge Anaconda-Cloud channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating metawrap-feedstock

If you would like to improve the metawrap 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 conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/metawrap-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

• @jakirkham

metawrap-feedstock's Issues

@conda-forge-admin, please re-render

@conda-forge-admin, please re-render.

Update version of metawrap

Hi,
I was wondering if it was possible to update metrawrap on conda-forge? Metawrap is at version 1.3 now, while the package on conda-forge is only at version 0.0.2.
There is a package on bioconda but with the current Bioconda installation instructions, the conda-forge channel is preferred over bioconda.

thanks!

"metawrap" package in bioconda

Hi @jakirkham ,

I am updating a package in bioconda named "metawrap". Since there is package with the same name, but completely different functionality in conda-forge, the linting gives the error "ERROR: recipes/metawrap/meta.yaml:5: in_other_channels: A package of the same name already exists in another channel", bioconda/bioconda-recipes#17324.

The bioinformatics package is https://github.com/bxlab/metaWRAP, so I was wondering whether is possible for this conda-forge package, since it is pure Python package, to be renamed to "py-metawrap" or something similar?
I looked at other recipes in conda-forge and bioconda, and didn't see either of the "metawrap" packages used as a dependency, which is a good thing.

Any feedback and suggestions on how to easier solve the linting issue is welcome!

Thank you,
Natasha