summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorElsa Gonsiorowski, PhD <gonsie@me.com>2018-12-21 02:03:54 -0800
committerTodd Gamblin <tgamblin@llnl.gov>2018-12-21 02:03:54 -0800
commit74a5d92f07dbc43e4cdabbdb30545ee27132eb5a (patch)
treefce7cf557ae86a595c269499fab1455eddc212c5
parent36ab7be4067613da1a6513e5701ce98ea4fee1a2 (diff)
downloadspack-74a5d92f07dbc43e4cdabbdb30545ee27132eb5a.tar.gz
spack-74a5d92f07dbc43e4cdabbdb30545ee27132eb5a.tar.bz2
spack-74a5d92f07dbc43e4cdabbdb30545ee27132eb5a.tar.xz
spack-74a5d92f07dbc43e4cdabbdb30545ee27132eb5a.zip
Remove /nfs/tmp2 from default build_stage locations (#10170)
* Remove /nfs/tmp2 from default configuration * /nfs/tmp2 is going away from LC... and doesn’t exist for the rest of the world. * update documentation to remove /nfs/tmp2 as well
-rw-r--r--etc/spack/defaults/config.yaml1
-rw-r--r--lib/spack/docs/config_yaml.rst10
2 files changed, 4 insertions, 7 deletions
diff --git a/etc/spack/defaults/config.yaml b/etc/spack/defaults/config.yaml
index 8525947fbd..8ccf7db535 100644
--- a/etc/spack/defaults/config.yaml
+++ b/etc/spack/defaults/config.yaml
@@ -48,7 +48,6 @@ config:
# The build stage can be purged with `spack clean --stage`.
build_stage:
- $tempdir
- - /nfs/tmp2/$user
- $spack/var/spack/stage
diff --git a/lib/spack/docs/config_yaml.rst b/lib/spack/docs/config_yaml.rst
index c02929d8c1..aaff130b7d 100644
--- a/lib/spack/docs/config_yaml.rst
+++ b/lib/spack/docs/config_yaml.rst
@@ -96,7 +96,6 @@ By default, Spack's ``build_stage`` is configured like this:
build_stage:
- $tempdir
- - /nfs/tmp2/$user
- $spack/var/spack/stage
This is an ordered list of paths that Spack should search when trying to
@@ -106,11 +105,10 @@ See :ref:`config-file-variables` for more on ``$tempdir`` and ``$spack``.
When Spack builds a package, it creates a temporary directory within the
``build_stage``, and it creates a symbolic link to that directory in
-``$spack/var/spack/stage``. This is used to track the stage.
-
-After a package is successfully installed, Spack deletes the temporary
-directory it used to build. Unsuccessful builds are not deleted, but you
-can manually purge them with :ref:`spack clean --stage
+``$spack/var/spack/stage``. This is used to track the temporary
+directory. After the package is successfully installed, Spack deletes
+the temporary directory it used to build. Unsuccessful builds are not
+deleted, but you can manually purge them with :ref:`spack clean --stage
<cmd-spack-clean>`.
.. note::