From 74a5d92f07dbc43e4cdabbdb30545ee27132eb5a Mon Sep 17 00:00:00 2001 From: "Elsa Gonsiorowski, PhD" Date: Fri, 21 Dec 2018 02:03:54 -0800 Subject: Remove /nfs/tmp2 from default build_stage locations (#10170) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * 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 --- lib/spack/docs/config_yaml.rst | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) (limited to 'lib') 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 `. .. note:: -- cgit v1.2.3-70-g09d2