Conversation
|
Note... this needs #2694 to be useful in real life. |
|
Does anyone have thoughts on this? I think it's a lot more interesting than #2705 |
|
I plan to look at this in the environments WG and after |
|
I wrote a similar patch for this in PR #6903 in Jan 2018, except that So, now I'm embarrassed that I didn't search the old PRs sufficiently. Anyway, I'm confident that you know more about spack than I do and Thanks, and be sure to nag Todd until his patch is committed. |
|
@mwkrentel This functionality has now been incorporated as part of the larger Spack Environments project. I encourage you to take a gander at #7843 and try it out; I am currently building my software stack based on that PR. In the meantime, I'm closing this PR: stacked scopes inside the Spack Environment are just nicer in so many ways that stacking them on the command line. |
Allows the user to add additional configuration scopes (beyond defaults/site/user) on the command line for all Spack commands. Docs are included in the PR, should be self-explanatory. I did this because I need it.
This addresses #2171, and gets a lot of functionality for a small number of lines of changed code.