-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
On appveyor, use already installed conda installations? #176
Comments
We already do that in But that is a nice idea to spread to other projects 😉 |
But why is it still using: https://github.com/conda-forge/conda-smithy/blob/master/conda_smithy/templates/appveyor.yml.tmpl#L49
|
Right. I missed that part. We should improve the smithy then. Not sure is the |
👍 on doing this. I'd like this to be a coherent part of the simplification we need to do to the feedstocks for 1.0. |
I just made the experience that updating conda also updates the python in the root env and that update takes ages on appveyor up to the point that I disabled updating conda again (conda/conda#1923 (comment)) . So it might be better to always start with a uptodate conda install... |
Though we already have to update I guess the only question is do we want to port over what we are doing at staged-recipes (pretty easy to do) or do we want to hold out for our own Miniconda? Personally I'd be ok porting this code over for the meantime if we are happy with it. Besides there are some Window issues we have to detangle before we can build |
The code used to do this at |
Also to reference the installer discussion. Please see issue ( conda-forge/conda-forge.github.io#90 ). |
See here for a transitioned recipe: matplotlib/matplotlib#6462
See also: appveyor/ci#359 which seens to be the issue implementing it (from https://twitter.com/tacaswell/status/734460129928712192)
The text was updated successfully, but these errors were encountered: