-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Add conda #656
Add conda #656
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Broke out the dependencies in this PR ( #657 ) so we can sort them out and get them in first. |
url: https://github.com/conda/conda/archive/{{ version }}.tar.gz | ||
sha256: 4ca7ec875de13519aeb3eebc9beca23adf3c41e8852c186deb503e8bc2282c40 | ||
|
||
build: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I remember correctly, you also need to always_include the conda executable: http://conda.pydata.org/docs/building/meta-yaml.html#force-files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, we are going to need to do that with a number of files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I'm wrong. We shouldn't need any as conda
does not live in this environment. Though we may run into a nasty situation with the conda
symlink. Care to comment on this point, @msarahan.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think bin/activate and bin/deactivate might need to be in the always_include
also, but this might only be needed on certain platforms.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the conda repository
# These are present when the new environment is created
# so we have to exempt them from the list of initial files
# for conda-build to realize they should be included.
always_include_files:
- bin/conda [unix]
- bin/activate [unix]
- bin/deactivate [unix]
- Scripts/activate.bat [win]
- Scripts/deactivate.bat [win]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
activate and deactivate both need to be in always_include (win needs them for bash support). Windows also needs the .bat files. There's a fish script, but I don't know where it goes. Issue here: conda/conda#2611
@jakirkham - indeed. Feel free to add me to all of these recipes. |
I can also provide the working recipes I have once I am back at my desk. |
@mcg1969, |
This is great! |
build: | ||
- python | ||
- conda-env | ||
- pycosat |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think these are build deps - I don't seem to need these in my own recipe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, this is required for the solver. I'm pretty sure it should be there. Care to comment on this, @mcg1969?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've never built a conda package for conda, frankly. These are certainly run dependencies but if it builds fine without them I see no reason to include them.
One thing about the conda-env
dependency: please look at our dependencies carefully. It's important that conda-env
and conda
remain in rough version lock-step. For instance, conda 4.1.x
requires conda-env >=2.5
, and conda 4.0.x
requires conda-env <2.5
.
We also use ruamel_yaml
for conda 4.1
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not adding the conda-env version dependencies can cause catastrophic issues if someone tries to downgrade.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, we had this chat before. This hasn't been touch in awhile. Thanks for the version pointers.
|
👍 in principle. I have a few review comments, but nothing show-stopping. |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
||
build: | ||
number: 0 | ||
script: python setup.py install |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this need an entry point?
entry_points:
- conda-env = conda_env.cli.main:main
The anaconda-recipes has it but not the repositories recipe
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably. 😄 Good point. Will add.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, actually does someone want to clarify this discrepancy?
Sorry for the barrage @jakirkham, would love to get this into |
e78b554
to
b6773de
Compare
I'm proposing to just not die if the files aren't there. They need to be there at the end, and we will clobber them if they are there. Nothing else matters. I don't think pinning this is breaking anything. I'm confused on how this works, anyway, since conda nominally won't install itself into non-root environments, but some of these scripts and entry points should actually only be present in environments with conda installed. |
Would commenting those Windows files in |
conda/conda-build#1101 implements the relaxation of always_include_files |
Restarting AppVeyor now that |
Just realized we are pinned to very old |
Broke out our work here on |
Is there any chance we could get |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
2240d81
to
8e8132a
Compare
So, I have fixed this up. It is now packaging the latest version of Also it seems to be pulling in During these changes, it was determined this now has a dependency on Some other changes were made like adding some more paths to the always include list. |
Thus far this seems to be passing on the CIs now (including AppVeyor). However, it fails on Windows Python 3.4 64-bit. This is actually not due to any problem with this recipe. Instead this is a consequence of our |
Closing and reopening to restart CIs. |
Now passing and ready to go. 😄 |
Adds recipes that either I wrote or used
conda skeleton pypi
to generate and then modified. Having some issue getting theconda
recipe to build. The rest seem to be doing ok. Maybe we can break out the working ones and merge them first.@msarahan, I have added you and myself as maintainers on all of these. Please let me know if that is ok. I don't feel a strong need to be a maintainer here, but I feel my handle should be on them as I wrote them.
@pelson, seemed like you were interested in seeing this happen. This gets the process started at least. If the going gets slow, feel free to take the reigns.