diff options
Diffstat (limited to 'etc')
| -rw-r--r-- | etc/spack/defaults/config.yaml | 19 |
1 files changed, 12 insertions, 7 deletions
diff --git a/etc/spack/defaults/config.yaml b/etc/spack/defaults/config.yaml index 33a37bbdfa..1b6d83f359 100644 --- a/etc/spack/defaults/config.yaml +++ b/etc/spack/defaults/config.yaml @@ -40,11 +40,8 @@ config: # Recommended options are given below. # # Builds can be faster in temporary directories on some (e.g., HPC) systems. - # Specifying `$tempdir` will ensure use of the system default temporary - # directory (as returned by `tempfile.gettempdir()`). Spack will append - # `spack-stage` and, if the username is not already in the path, the value - # of `$user` to the path. The latter is used to avoid conflicts between - # users in shared temporary spaces. + # Specifying `$tempdir` will ensure use of the default temporary directory + # (i.e., ``$TMP` or ``$TMPDIR``). # # Another option that prevents conflicts and potential permission issues is # to specify `~/.spack/stage`, which ensures each user builds in their home @@ -52,13 +49,21 @@ config: # # A more traditional path uses the value of `$spack/var/spack/stage`, which # builds directly inside Spack's instance without staging them in a - # temporary space. + # temporary space. Problems with specifying a path inside a Spack instance + # are that it precludes its use as a system package and its ability to be + # pip installable. + # + # In any case, if the username is not already in the path, Spack will append + # the value of `$user` in an attempt to avoid potential conflicts between + # users in shared temporary spaces. # # The build stage can be purged with `spack clean --stage` and # `spack clean -a`, so it is important that the specified directory uniquely # identifies Spack staging to avoid accidentally wiping out non-Spack work. build_stage: - - $tempdir/spack-stage + - $tempdir/$user/spack-stage + - ~/.spack/stage + # - $spack/var/spack/stage # Cache directory for already downloaded source tarballs and archived |