-
Notifications
You must be signed in to change notification settings - Fork 47
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
Make use of "excludes" for modules? #197
Comments
Thanks! Yes, I saw that as well and took notes. I’d say post release v1 if that’s ok with you?
… On Jun 10, 2022, at 1:35 PM, Kyle Gerheiser ***@***.***> wrote:
@climbfuji <https://github.com/climbfuji> this is from that video you sent about Spack, and one of the slides mentioned using blacklists_implicits. I tried this out myself and it's pretty useful.
Modules will only be generated for explicit (or whitelist:) specs, and then the giant blacklist we have can be cut down to just what we want.
—
Reply to this email directly, view it on GitHub <#197>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5C2RNUL6CONH5AYJRSLWTVOOKGTANCNFSM5YOUZOOQ>.
You are receiving this because you were mentioned.
|
climbfuji
added
NAVY
United States Naval Research Lab
and removed
INFRA
JEDI Infrastructure
labels
Apr 30, 2024
climbfuji
changed the title
Make use of blacklist_implicits for modules?
Make use of "excludes" for modules?
Sep 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@climbfuji this is from that video you sent about Spack, and one of the slides mentioned using
blacklists_implicits: true
. I tried this out myself and it's pretty useful.Modules will only be generated for explicit (or
whitelist:
) specs, and then the giantblacklist
we have can be cut down. Instead of blacklisting what we don't want, it might be more useful to whitelist what we do want.The text was updated successfully, but these errors were encountered: