-
Notifications
You must be signed in to change notification settings - Fork 17
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
Discuss the use of miniconda for installing dependencies #4
Comments
Thanks for filing issues from the comment of #1 so fast. It is so fast that I thought it was done by some github feature. : ) |
Impressive. Thanks a lot, @j8xixo12 . |
In my opinion, the most straightforward implementation is to build each package of conda from source one by one. At the very beginning we use conda. In the end we may build as many packages from source on our own as possible. |
That sounds like duplicating what conda forge does. Besides, it doesn't sound like to allow multiple DEs (rel, dbg, etc.) in parallel? |
The discussion of #13 (comment) make me recall this thread. Sorry for the late reply.
I am not sure if we are on the same page. For me, it is
I did not follow the last question. What did you mean by "not allow multiple DEs (rel, dbg, etc.) in parallel? Why? |
Agree that when
I meant, the conda builder doesn't seem to allow building different flavors (rel/dbg). But I am not sure. Does it? |
Cool! We are on the same page : D
I see. I am not sure too. My gut feeling is "no, it doesn't". |
I realize that this page here is an issue but we actually have repository discussions set up. Let's move the discussions there: #14 . |
This script uses miniconda for most of the dependencies so I think it's probably good to highlight it in the filename. We may do it with this PR or act after more discussions.
Originally posted by @yungyuc in #1 (comment)
The text was updated successfully, but these errors were encountered: