summaryrefslogtreecommitdiff
path: root/NOTICE
diff options
context:
space:
mode:
authorMassimiliano Culpo <massimiliano.culpo@googlemail.com>2017-10-05 03:14:06 +0200
committerscheibelp <scheibel1@llnl.gov>2017-10-04 18:14:06 -0700
commit3556eaae7e07379b811bdf0f8672db42b64a4476 (patch)
tree1de8b81fae4ef380c16a51ed518470d96bd3ab73 /NOTICE
parent395000c3856cb9d61c9bb58960e6f19884444132 (diff)
downloadspack-3556eaae7e07379b811bdf0f8672db42b64a4476.tar.gz
spack-3556eaae7e07379b811bdf0f8672db42b64a4476.tar.bz2
spack-3556eaae7e07379b811bdf0f8672db42b64a4476.tar.xz
spack-3556eaae7e07379b811bdf0f8672db42b64a4476.zip
module files: restricted token expansion + case sensitivity (#5474)
closes #2884 closes #4684 In #1848 we decided to use `Spec.format` to expand certain tokens in the module file naming scheme or in the environment variable name. Not all the tokens that are allowed in `Spec.format` make sense in module file generation. This PR restricts the set of tokens that can be used, and adds tests to check that the intended behavior is respected. Additionally, the names of environment variables set/modified by module files were, up to now, always uppercase. There are packages though that require case sensitive variable names to honor certain behaviors (e.g. OpenMPI). This PR restricts the uppercase transformation in variable names to `Spec.format` tokens.
Diffstat (limited to 'NOTICE')
0 files changed, 0 insertions, 0 deletions