Awesome

About conda-lock-feedstock

Feedstock license: BSD-3-Clause

Home: https://github.com/conda/conda-lock

Package license: MIT

Summary: Lightweight lockfile for conda environments

Documentation: https://conda.github.io/conda-lock/

Conda lock is a lightweight library that can be used to generate fully reproducible lock files for conda environments. It does this by performing multiple solves for conda targeting a set of platforms you desire lockfiles for. This also has the added benefit of acting as an external presolve for conda as the lockfiles it generates results in the conda solver not being invoked when installing the packages from the generated lockfile.

Current build status

<table><tr><td>All platforms:</td> <td> <a href="https://dev.azure.com/conda-forge/feedstock-builds/_build/latest?definitionId=9912&branchName=main"> <img src="https://dev.azure.com/conda-forge/feedstock-builds/_apis/build/status/conda-lock-feedstock?branchName=main"> </a> </td> </tr> </table>

Current release info

Name	Downloads	Version	Platforms

Installing conda-lock

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

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

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

conda install conda-lock

or with mamba:

mamba install conda-lock

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

conda search conda-lock --channel conda-forge

or with mamba:

mamba search conda-lock --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search conda-lock --channel conda-forge

# List packages depending on `conda-lock`:
mamba repoquery whoneeds conda-lock --channel conda-forge

# List dependencies of `conda-lock`:
mamba repoquery depends conda-lock --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 Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org 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 conda-lock-feedstock

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