About mamba-split-feedstock
Feedstock license: BSD-3-Clause
About mamba-split
Home: https://github.com/mamba-org/mamba
Package license: BSD-3-Clause
Summary: A fast drop-in alternative to conda, using libsolv for dependency resolution
Development: https://github.com/mamba-org/mamba
Mamba, the Fast Cross-Platform Package Manager
mamba is a reimplementation of the conda package manager in C++.
- parallel downloading of repository data and package files using multi-threading
- libsolv for much faster dependency solving, a state of the art library used in the RPM package manager of Red Hat, Fedora and OpenSUSE
- core parts of
mambaare implemented in C++ for maximum efficiency
At the same time, mamba utilizes the same command line parser, package installation and deinstallation code and transaction verification routines as conda to stay as compatible as possible.
Mamba is part of a bigger ecosystem to make scientific packaging more sustainable. You can read our announcement blog post.
The ecosystem also consists of quetz, an open source conda package server and boa, a fast conda package builder.
Installation
Please refer to the mamba and micromamba installation guide in the documentation.
Additional features in Mamba and Micromamba
mamba and micromamba come with features on top of stock conda.
repoquery
To efficiently query repositories and query package dependencies you can use mamba repoquery or micromamba repoquery.
See the repoquery documentation for details.
Installing lock files
micromamba can be used to install lock files generated by conda-lock without having to install conda-lock. Simply invoke e.g. micromamba create -n my-env -f conda-lock.yml with an environment lockfile named *-lock.yml or *-lock.yaml.
About libmamba
Home: https://github.com/mamba-org/mamba
Package license: BSD-3-Clause
Summary: A fast drop-in alternative to conda, using libsolv for dependency resolution
Development: https://github.com/mamba-org/mamba
mamba is a reimplementation of the conda package manager in C++.
- parallel downloading of repository data and package files using multi-threading
- libsolv for much faster dependency solving, a state of the art library used in the RPM package manager of Red Hat, Fedora and OpenSUSE
- core parts of
mambaare implemented in C++ for maximum efficiency
At the same time, mamba utilizes the same command line parser, package installation and deinstallation code and transaction verification routines as conda to stay as compatible as possible.
Mamba is part of a bigger ecosystem to make scientific packaging more sustainable. You can read our announcement blog post.
The ecosystem also consists of quetz, an open source conda package server and boa, a fast conda package builder.
Please refer to the mamba and micromamba installation guide in the documentation.
mamba and micromamba come with features on top of stock conda.
To efficiently query repositories and query package dependencies you can use mamba repoquery or micromamba repoquery.
See the repoquery documentation for details.
micromamba can be used to install lock files generated by conda-lock without having to install conda-lock. Simply invoke e.g. micromamba create -n my-env -f conda-lock.yml with an environment lockfile named *-lock.yml or *-lock.yaml.
About libmambapy
Home: https://github.com/mamba-org/mamba
Package license: BSD-3-Clause
Summary: A fast drop-in alternative to conda, using libsolv for dependency resolution
Development: https://github.com/mamba-org/mamba
mamba is a reimplementation of the conda package manager in C++.
- parallel downloading of repository data and package files using multi-threading
- libsolv for much faster dependency solving, a state of the art library used in the RPM package manager of Red Hat, Fedora and OpenSUSE
- core parts of
mambaare implemented in C++ for maximum efficiency
At the same time, mamba utilizes the same command line parser, package installation and deinstallation code and transaction verification routines as conda to stay as compatible as possible.
Mamba is part of a bigger ecosystem to make scientific packaging more sustainable. You can read our announcement blog post.
The ecosystem also consists of quetz, an open source conda package server and boa, a fast conda package builder.
Please refer to the mamba and micromamba installation guide in the documentation.
mamba and micromamba come with features on top of stock conda.
To efficiently query repositories and query package dependencies you can use mamba repoquery or micromamba repoquery.
See the repoquery documentation for details.
micromamba can be used to install lock files generated by conda-lock without having to install conda-lock. Simply invoke e.g. micromamba create -n my-env -f conda-lock.yml with an environment lockfile named *-lock.yml or *-lock.yaml.
Current build status
| Azure |
|
Current release info
| Name | Downloads | Version | Platforms |
|---|---|---|---|
 |
 |
 |
 |
 |
 |
 |
 |
Installing mamba-split
Installing mamba-split from the conda-forge/label/mamba_dev channel can be achieved by adding conda-forge/label/mamba_dev to your channels with:
conda config --add channels conda-forge/label/mamba_dev
conda config --set channel_priority strict
Once the conda-forge/label/mamba_dev channel has been enabled, libmamba, libmambapy can be installed with conda:
conda install libmamba libmambapy
or with mamba:
mamba install libmamba libmambapy
It is possible to list all of the versions of libmamba available on your platform with conda:
conda search libmamba --channel conda-forge/label/mamba_dev
or with mamba:
mamba search libmamba --channel conda-forge/label/mamba_dev
Alternatively, mamba repoquery may provide more information:
# Search all versions available on your platform:
mamba repoquery search libmamba --channel conda-forge/label/mamba_dev
# List packages depending on `libmamba`:
mamba repoquery whoneeds libmamba --channel conda-forge/label/mamba_dev
# List dependencies of `libmamba`:
mamba repoquery depends libmamba --channel conda-forge/label/mamba_dev
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 mamba-split-feedstock
If you would like to improve the mamba-split 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/mamba-split-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/numberback to 0.