Feedstock license: BSD-3-Clause
Home: https://github.com/conda-forge/microarch-level-feedstock
Package license: BSD-3-Clause
Summary: Meta package to build conda recipes with microarchitecture levels
Home: https://github.com/conda-forge/microarch-level-feedstock
Package license: BSD-3-Clause
Summary: Meta package to build conda recipes with microarchitecture levels
The meta-package _x86_64-microarch-level enforces the microarchitecture in the user system.
Note that a user would need the archspec conda package installed in the base environment where conda/mamba is run from.
See x86_64-microarch-level for using this in conda recipes
Home: https://github.com/conda-forge/microarch-level-feedstock
Package license: BSD-3-Clause
Summary: Meta package to build conda recipes with microarchitecture levels
Use the meta-package x86_64-microarch-level in requirements/build in conda recipes to set up the compiler flags and set up the virtual package requirements in the run requirements.
When building packages on CI, level=4 will not be guaranteed, so you can only use level<=3 to build.
The run_exports only has a lower bound and therefore a level=2 build can be installed on a level=3 user system. A tighter bound is not added because we want to be able to test both level=2 and level=3 on a CI machine with level=3. Therefore in order to prioritise the highest level, use the build number to prioritise the level.
Only supported on Linux and macOS.
Home: https://github.com/conda-forge/microarch-level-feedstock
Package license: BSD-3-Clause
Summary: Meta package to build conda recipes with microarchitecture levels
The meta-package _ppc64le-microarch-level enforces the microarchitecture in the user system.
Note that a user would need the archspec conda package installed in the base environment where conda/mamba is run from.
See ppc64le-microarch-level for using this in conda recipes
Home: https://github.com/conda-forge/microarch-level-feedstock
Package license: BSD-3-Clause
Summary: Meta package to build conda recipes with microarchitecture levels
Use the meta-package ppc64le-microarch-level in requirements/build in conda recipes to set up the compiler flags and set up the virtual package requirements in the run requirements.
When building packages on CI, level=4 will not be guaranteed, so you can only use level<=3 to build.
The run_exports only has a lower bound and therefore a level=2 build can be installed on a level=3 user system. A tighter bound is not added because we want to be able to test both level=2 and level=3 on a CI machine with level=3. Therefore in order to prioritise the highest level, use the build number to prioritise the level.
Only supported on Linux and macOS.
| All platforms: |
|
| Name | Downloads | Version | Platforms |
|---|---|---|---|
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Installing microarch-level 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, _ppc64le-microarch-level, _x86_64-microarch-level, ppc64le-microarch-level, x86_64-microarch-level can be installed with conda:
conda install _ppc64le-microarch-level _x86_64-microarch-level ppc64le-microarch-level x86_64-microarch-level
or with mamba:
mamba install _ppc64le-microarch-level _x86_64-microarch-level ppc64le-microarch-level x86_64-microarch-level
It is possible to list all of the versions of _ppc64le-microarch-level available on your platform with conda:
conda search _ppc64le-microarch-level --channel conda-forge
or with mamba:
mamba search _ppc64le-microarch-level --channel conda-forge
Alternatively, mamba repoquery may provide more information:
# Search all versions available on your platform:
mamba repoquery search _ppc64le-microarch-level --channel conda-forge
# List packages depending on `_ppc64le-microarch-level`:
mamba repoquery whoneeds _ppc64le-microarch-level --channel conda-forge
# List dependencies of `_ppc64le-microarch-level`:
mamba repoquery depends _ppc64le-microarch-level --channel 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.
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)
If you would like to improve the microarch-level 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/microarch-level-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.