Skip to content

Disable module file generation by default#37258

Merged
alalazo merged 5 commits intospack:developfrom
alalazo:features/disable_module_file_generation
May 2, 2023
Merged

Disable module file generation by default#37258
alalazo merged 5 commits intospack:developfrom
alalazo:features/disable_module_file_generation

Conversation

@alalazo
Copy link
Copy Markdown
Member

@alalazo alalazo commented Apr 27, 2023

This follows a poll done in Slack over a month ago.

Modifications:

This is an example of a custom modules.yaml triggering a warning + an example of "normal" working mode:
Screenshot from 2023-04-27 21-02-59

haampie and others added 3 commits April 27, 2023 19:08
a) It's used by site administrators, so it's niche
b) If it's used by site administrators, they likely need to modify the config anyhow, so the default config only serves as an example to get started
c) it's too arbitrary to enable tcl, but disable lmod
@spackbot-app spackbot-app bot added core PR affects Spack core functionality defaults modules labels Apr 27, 2023
@haampie
Copy link
Copy Markdown
Member

haampie commented Apr 28, 2023

Maybe this is too much, but can the warning be narrowed to tcl? Also useful to say how to enable it

@alalazo
Copy link
Copy Markdown
Member Author

alalazo commented Apr 28, 2023

Maybe this is too much, but can the warning be narrowed to tcl? Also useful to say how to enable it

I'll check that. There's potentially another case where this can emit spurious warnings, i.e. somebody that for any unknown reason is deliberately not using the "default" module set, but others. I didn't consider that case because I don't see where it could make sense to do that, since the module set name is never exposed anywhere in the generated modules.

@alalazo
Copy link
Copy Markdown
Member Author

alalazo commented Apr 28, 2023

Latest version:
Screenshot from 2023-04-28 19-38-50

@alalazo alalazo requested a review from haampie May 1, 2023 07:08
@alalazo alalazo added this to the v0.20.0 milestone May 1, 2023
@alalazo
Copy link
Copy Markdown
Member Author

alalazo commented May 1, 2023

@spackbot run pipeline

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented May 1, 2023

I've started that pipeline for you!

@alalazo
Copy link
Copy Markdown
Member Author

alalazo commented May 1, 2023

@spackbot run pipeline

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented May 1, 2023

I've started that pipeline for you!

@alalazo alalazo merged commit a92f1e3 into spack:develop May 2, 2023
@alalazo alalazo deleted the features/disable_module_file_generation branch May 2, 2023 08:28
joequant pushed a commit to hkphysics/spack that referenced this pull request May 2, 2023
* Disable module generation by default (spack#35564)

a) It's used by site administrators, so it's niche
b) If it's used by site administrators, they likely need to modify the config anyhow, so the default config only serves as an example to get started
c) it's too arbitrary to enable tcl, but disable lmod

* Remove leftover from old module file schema

* Warn if module file config is detected and generation is disabled

---------

Co-authored-by: Harmen Stoppels <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core PR affects Spack core functionality defaults modules

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants