Update setup.sh: add export SPACK_DISABLE_LOCAL_CONFIG=true#1545
Update setup.sh: add export SPACK_DISABLE_LOCAL_CONFIG=true#1545climbfuji merged 4 commits intoJCSDA:developfrom
Conversation
…letely isolate the spack-stack environments from user spack configurations (JCSDA#60)
|
Ooops, I remember. The problem was this didn't work for new site configs, because we use |
…sing ~/.spack also on macOS
…CK_DISABLE_LOCAL_CONFIG
|
I fixed this in 2e91ad6, a17b244, and d42cf47 by adding one more step to the NewSiteConfig instructions (unset I also removed the exception to skip avoiding ~/.spack for macOS. We needed this in the past when bootstrapping was a tedious and manual process, but fortunately this is no longer the case. I tested this on the macOS CI runner manally. Hopefully, it will work just as well in CI. |
srherbener
left a comment
There was a problem hiding this comment.
I think this looks good. I did not test, rather I'm relying on the CI testing and others. I like that by default user configuration is ignored for the build, and only for customized (new site config) builds you can temporarily enable user configuration. Thanks!
Summary
Update
setup.sh: addexport SPACK_DISABLE_LOCAL_CONFIG=trueto completely isolate the spack-stack environments from user spack configurations. This requires additional steps to unset and restore the environment variable when creating new site configurations. Further, remove the exception for macOS (no longer needed, see #1545 (comment) below for more information)Testing
Applications affected
None
Systems affected
"All" (not really), but at least air-gapped systems where the spack bootstrap mirror needs to be used every time from now on.
Dependencies
n/a
Issue(s) addressed
Closes #1544
Checklist
All dependency PRs/issues have been resolved and this PR can be merged.