Skip to content

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

Open
wolfv opened this issue Jun 7, 2024 · 5 comments · May be fixed by #1669
Open

Package content tests - add exists / not_exists #915

wolfv opened this issue Jun 7, 2024 · 5 comments · May be fixed by #1669

Comments

@wolfv
Copy link
Member

wolfv commented Jun 7, 2024

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:

package_content:
  include:
    exists: 
      - foo.hpp
    not_exists:
      - baz.hpp
@wolfv
Copy link
Member Author

wolfv commented Jun 7, 2024

Note: this reflects includes and excludes from the regular "glob" places.

@minrk
Copy link
Contributor

minrk commented Apr 25, 2025

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.

@beckermr
Copy link

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.

@minrk
Copy link
Contributor

minrk commented Apr 25, 2025

Yes, I believe the CEP for this is here: conda/ceps#84

@beckermr
Copy link

Cool. It needs to be put up for a vote and passed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants