-
Notifications
You must be signed in to change notification settings - Fork 79
Package content tests - add exists / not_exists
#915
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
Comments
Note: this reflects |
Just ran into this, and it would indeed be nice. The most common exclusion check I think I have in recipes is making sure static libs aren't being installed, or e.g. any include files or any libs when e.g. headers and things are split into multiple outputs. |
We need to not make arbitray changes to the yaml. Otherwise other tools won't be able to process the recipes. These kinds of changes should be submitted as a CEP. |
Yes, I believe the CEP for this is here: conda/ceps#84 |
Cool. It needs to be put up for a vote and passed. |
Sometimes you want to check that a file is there and sometimes the inverse.
We had ideas to use
~ foo.txt
to say 'not exists' but people were against it.Instead, let's use a dictionary like so:
The text was updated successfully, but these errors were encountered: