Skip to content

Latest commit

 

History

History
108 lines (75 loc) · 3.63 KB

README.md

File metadata and controls

108 lines (75 loc) · 3.63 KB
Raw

About nocuda11-feedstock

Feedstock license: BSD-3-Clause

Home: https://github.com/ramonaoptics/nocuda11-feedstock

Package license: BSD-3-Clause

Summary: prevents installation of cuda 11

Current build status

All platforms:

Current release info

Name Downloads Version Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms

Installing nocuda11

Installing nocuda11 from the ramonaoptics channel can be achieved by adding ramonaoptics to your channels with:

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

Once the ramonaoptics channel has been enabled, nocuda11 can be installed with conda:

conda install nocuda11

or with mamba:

mamba install nocuda11

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

conda search nocuda11 --channel ramonaoptics

or with mamba:

mamba search nocuda11 --channel ramonaoptics

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search nocuda11 --channel ramonaoptics

# List packages depending on `nocuda11`:
mamba repoquery whoneeds nocuda11 --channel ramonaoptics

# List dependencies of `nocuda11`:
mamba repoquery depends nocuda11 --channel ramonaoptics

Updating nocuda11-feedstock

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