-
Notifications
You must be signed in to change notification settings - Fork 119
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
fix(mamba) #414
base: main
Are you sure you want to change the base?
fix(mamba) #414
Conversation
ddobrinskiy
commented
Feb 20, 2023
•
edited
Loading
edited
- resolve errors in mamba (is it relocatable?) #413 (certificate errors)
- rewrite tests to check the actual package functionality
…e opt/ links" This reverts commit 0647a38.
So why is it we’re using this pre packaged mamba forge thing rather than building our own? I'm sure there's good reason but the comment doesn't actually specify it and I think we should add it. |
Yeah so… 878 hard coded prefixes… This thing is bundled with a lot of packages we provide ourselves. I'm not familiar enough with python AI stuff yet to understand if we can break it apart, but I'm investigating. Though I will start with anaconda |
I'm not sure there's actually an easy way to do that, the official docs basically say "just use older mamba to build newer version from source" So brew also uses the pre-packaged version |
My intuition is that we should not break it apart, because the idea of mamba is to provide multiple isolated enviroments, like venv. The same way you would not want your |
it's a brew cask, which means it's just a slight convenience wrapper around a pre-packaged thing. So it's not really packaged by brew in other words. We can do better. I will tackle this sooooonish I hope. Got a lot of balls in the air RN |
I managed to pkg I have begun trying to package this from first steps as well. Mostly I'm struggling with understanding their install instructions since they seem to assume you have some kind of conda env already setup. |