summaryrefslogtreecommitdiff
path: root/lib/spack/docs/packaging_guide.rst
diff options
context:
space:
mode:
authorMassimiliano Culpo <massimiliano.culpo@googlemail.com>2017-08-09 19:02:38 +0200
committerbecker33 <becker33@llnl.gov>2017-08-09 10:02:38 -0700
commitfaeb1b77b2a5c5188b0d765c337c342dc2b8fd35 (patch)
tree63a98c70d144e61f9d948ec09a73e2c3279327d0 /lib/spack/docs/packaging_guide.rst
parent9e8cce41e3f78ed4222eff342a5b61b6f8fbf645 (diff)
downloadspack-faeb1b77b2a5c5188b0d765c337c342dc2b8fd35.tar.gz
spack-faeb1b77b2a5c5188b0d765c337c342dc2b8fd35.tar.bz2
spack-faeb1b77b2a5c5188b0d765c337c342dc2b8fd35.tar.xz
spack-faeb1b77b2a5c5188b0d765c337c342dc2b8fd35.zip
Merged 'purge' command with 'clean' and deleted 'purge' (#4970)
* Merged 'purge' command with 'clean'. Deleted 'purge'. fixes #2942 'spack purge' has been merged with 'spack clean'. Documentation has been updated accordingly. The 'clean' and 'purge' behavior are not mutually exclusive, and they log brief information to tty while they go. * Fixed a wrong reference to spack clean in the docs * Added tests for 'spack clean'. Updated bash completion.
Diffstat (limited to 'lib/spack/docs/packaging_guide.rst')
-rw-r--r--lib/spack/docs/packaging_guide.rst21
1 files changed, 7 insertions, 14 deletions
diff --git a/lib/spack/docs/packaging_guide.rst b/lib/spack/docs/packaging_guide.rst
index af3f7b408a..7e789bc294 100644
--- a/lib/spack/docs/packaging_guide.rst
+++ b/lib/spack/docs/packaging_guide.rst
@@ -3432,24 +3432,12 @@ Does this in one of two ways:
``spack clean``
^^^^^^^^^^^^^^^
-Cleans up temporary files for a particular package, by deleting the
-expanded/checked out source code *and* any downloaded archive. If
-``fetch``, ``stage``, or ``install`` are run again after this, Spack's
-build process will start from scratch.
-
-.. _cmd-spack-purge:
-
-^^^^^^^^^^^^^^^
-``spack purge``
-^^^^^^^^^^^^^^^
-
Cleans up all of Spack's temporary and cached files. This can be used to
recover disk space if temporary files from interrupted or failed installs
accumulate in the staging area.
When called with ``--stage`` or without arguments this removes all staged
-files and will be equivalent to running ``spack clean`` for every package
-you have fetched or staged.
+files.
When called with ``--downloads`` this will clear all resources
:ref:`cached <caching>` during installs.
@@ -3459,6 +3447,11 @@ directory, including cached virtual indices.
To remove all of the above, the command can be called with ``--all``.
+When called with positional arguments, cleans up temporary files only
+for a particular package. If ``fetch``, ``stage``, or ``install``
+are run again after this, Spack's build process will start from scratch.
+
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Keeping the stage directory on success
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -3472,7 +3465,7 @@ package has been successfully built and installed. Use
$ spack install --keep-stage <spec>
This allows you to inspect the build directory and potentially debug
-the build. You can use ``purge`` or ``clean`` later to get rid of the
+the build. You can use ``clean`` later to get rid of the
unwanted temporary files.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^