diff options
| author | Harmen Stoppels <harmenstoppels@gmail.com> | 2021-10-11 16:07:45 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-10-11 09:07:45 -0500 |
| commit | 89220bc0e1bc8df0130cf5388488c2b161caf554 (patch) | |
| tree | d7fca96dd6a47c87b0e5fbd1c03d6142941da042 /NOTICE | |
| parent | c0c9ab113e0078c53e60df6cb7cb064e6f92c45b (diff) | |
| download | spack-89220bc0e1bc8df0130cf5388488c2b161caf554.tar.gz spack-89220bc0e1bc8df0130cf5388488c2b161caf554.tar.bz2 spack-89220bc0e1bc8df0130cf5388488c2b161caf554.tar.xz spack-89220bc0e1bc8df0130cf5388488c2b161caf554.zip | |
Only install env modifications in <prefix>/.spack (#24081)
- Do not store the full list of environment variables in
<prefix>/.spack/spack-build-env.txt because it may contain user secrets.
- Only store environment variable modifications upon installation.
- Variables like PATH may still contain user and system paths to make
spack-build-env.txt sourceable. Variables containing paths are
modified through prepending/appending, and if we don't apply these
to the current environment variable, we end up with statements like
`export PATH=/path/to/spack/bin` with system paths missing, meaning
no system binaries are in the path, which is a bad user experience.
- Do write the full environment to spack-build-env.txt in the staging dir,
but ensure it is readonly for the current user, to make it a bit safer
on shared systems.
Diffstat (limited to 'NOTICE')
0 files changed, 0 insertions, 0 deletions