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

Rethink interaction of all conda-related tooling in conda-store #758

Open
nkaretnikov opened this issue Feb 1, 2024 · 0 comments
Open

Comments

@nkaretnikov
Copy link
Contributor

nkaretnikov commented Feb 1, 2024

Context

@jaimergp suggested I open this for discussing long-term plans for conda-store with regard to how conda tools are used.
Right now, we use conda as a library, via conda-lock, and via constructor.
All these know nothing about each other (only implicitly, e.g., via a shared global conda cache), which might lead to problems.
For example, #745 (comment) was discovered because conda-store and conda-lock didn't communicate, so the shared cache was not used, which led to everything being downloaded on every build.

Value and/or benefit

Better performance and reliability.

Anything else?

No response

@nkaretnikov nkaretnikov added needs: triaging 🚦 Someone needs to have a look at this issue and triage type: enhancement 💅🏼 needs: discussion 💬 area: configuration area: dependencies 📦 Issues related to conda-store dependencies area: user experience 👩🏻‍💻 Items impacting the end-user experience type: maintenance 🛠 and removed needs: triaging 🚦 Someone needs to have a look at this issue and triage labels Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: TODO 📬
Development

No branches or pull requests

2 participants