diff options
| author | Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com> | 2019-10-16 14:55:37 -0700 |
|---|---|---|
| committer | Peter Scheibel <scheibel1@llnl.gov> | 2019-10-16 14:55:37 -0700 |
| commit | 1ef71376f2e2b41229471501e91448858f2df61d (patch) | |
| tree | 053564e6d2be89c0ac3c71c818e4c4e34c8c7589 /lib/spack/docs/config_yaml.rst | |
| parent | e17df2e8f5dd46ef1c08252c08bdda191b64d911 (diff) | |
| download | spack-1ef71376f2e2b41229471501e91448858f2df61d.tar.gz spack-1ef71376f2e2b41229471501e91448858f2df61d.tar.bz2 spack-1ef71376f2e2b41229471501e91448858f2df61d.tar.xz spack-1ef71376f2e2b41229471501e91448858f2df61d.zip | |
Bugfix: stage directory permissions and cleaning (#12733)
* This updates stage names to use "spack-stage-" as a prefix.
This avoids removing non-Spack directories in "spack clean" as
c141e99 did (in this case so long as they don't contain the
prefix "spack-stage-"), and also addresses a follow-up issue
where Spack stage directories were not removed.
* Spack now does more-stringent checking of expected permissions for
staging directories. For a given stage root that includes a user
component, all directories before the user component that are
created by Spack are expected to match the permissions of their
parent; the user component and all deeper directories are expected
to be accessible to the user (read/write/execute).
Diffstat (limited to 'lib/spack/docs/config_yaml.rst')
| -rw-r--r-- | lib/spack/docs/config_yaml.rst | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/lib/spack/docs/config_yaml.rst b/lib/spack/docs/config_yaml.rst index 53398f55c2..525f829c9e 100644 --- a/lib/spack/docs/config_yaml.rst +++ b/lib/spack/docs/config_yaml.rst @@ -91,9 +91,10 @@ the selected ``build_stage`` path. .. warning:: We highly recommend specifying ``build_stage`` paths that distinguish between staging and other activities to ensure ``spack clean`` does not inadvertently remove unrelated files. - This can be accomplished by using a combination of ``spack`` and or - ``stage`` in each path as shown in the default settings and documented - examples. + Spack prepends ``spack-stage-`` to temporary staging directory names to + reduce this risk. Using a combination of ``spack`` and or ``stage`` in + each specified path, as shown in the default settings and documented + examples, will add another layer of protection. By default, Spack's ``build_stage`` is configured like this: |