summaryrefslogtreecommitdiff
path: root/NOTICE
diff options
context:
space:
mode:
authorPeter Scheibel <scheibel1@llnl.gov>2021-06-24 16:13:46 -0700
committerGitHub <noreply@github.com>2021-06-24 16:13:46 -0700
commit916cdfbb56b2abfc380ce1b4cac0d6494b7f2628 (patch)
tree68f2417af733227274d4a228c30509fbea1462e9 /NOTICE
parentd7405ddd3908f328d052d1de7520620924825b7b (diff)
downloadspack-916cdfbb56b2abfc380ce1b4cac0d6494b7f2628.tar.gz
spack-916cdfbb56b2abfc380ce1b4cac0d6494b7f2628.tar.bz2
spack-916cdfbb56b2abfc380ce1b4cac0d6494b7f2628.tar.xz
spack-916cdfbb56b2abfc380ce1b4cac0d6494b7f2628.zip
Environment modifications: de-prioritize external packages (#23824)
Prior to any Spack build, Spack modifies PATH etc. to help the build find the dependencies it needs. It also allows any package to define custom environment modifications (and furthermore a package can specify environment modifications to apply when it is used as a dependency). If an external package defines custom environment modifications that alter PATH, and the external package is in a merged or system prefix, then that prefix could "override" the Spack-built packages. This commit reorders environment modifications so that PrependPath actions which expose Spack-built packages override PrependPath actions for custom environment modifications of external packages. In more detail, the original order of environment modifications is: * Modules * Compiler flag variables * PATH, CMAKE_PREFIX_PATH, and PKG_CONFIG_PATH for dependencies * Custom package.py modifications in the following order: * dependencies * root This commit changes the order: * Modules * Compiler flag variables * For each external dependency * PATH, CMAKE_PREFIX_PATH, and PKG_CONFIG_PATH modifications * Custom modifications * For each Spack-built dependency * PATH, CMAKE_PREFIX_PATH, and PKG_CONFIG_PATH modifications * Custom modifications
Diffstat (limited to 'NOTICE')
0 files changed, 0 insertions, 0 deletions