Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to set channel_priority when building an installer? #778

Closed
moorepants opened this issue Apr 23, 2024 · 2 comments
Closed

How to set channel_priority when building an installer? #778

moorepants opened this issue Apr 23, 2024 · 2 comments
Labels
locked [bot] locked due to inactivity

Comments

@moorepants
Copy link

This is just a question I have. Sorry if issues is the wrong location to ask it.

Is there a way to have conda's solver honor channel_priority: strict when calling constructor .? The only thing I could find in the docs was the condarc option but that seems to drop a condarc file in the base installation after installing, so that these settings would be applied to users of the installation. How would I go about enforcing this setting when building the installer?

@jaimergp
Copy link
Contributor

jaimergp commented May 8, 2024

It should inherit your system condarc. You can also use the CONDA_* env vars for this. In this case CONDA_CHANNEL_PRIORITY=strict, I think?

@moorepants
Copy link
Author

I see. The issue I'm trying to address is that we have multiple people build the installer for testing and I want to ensure that everyone builds with the same conda settings. So it sounds like I need them to do something like:

CONDA_CHANNEL_PRIORITY=strict constructor .

to ensure any local settings they have in their condarc are overwritten. I'll give that a go.

@github-project-automation github-project-automation bot moved this from 🆕 New to 🏁 Done in 🧭 Planning May 13, 2024
@github-actions github-actions bot added the locked [bot] locked due to inactivity label Nov 9, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity
Projects
Archived in project
Development

No branches or pull requests

2 participants