summaryrefslogtreecommitdiff
path: root/lib/spack/docs
diff options
context:
space:
mode:
Diffstat (limited to 'lib/spack/docs')
-rw-r--r--lib/spack/docs/packaging_guide.rst11
1 files changed, 9 insertions, 2 deletions
diff --git a/lib/spack/docs/packaging_guide.rst b/lib/spack/docs/packaging_guide.rst
index 840c29454b..1f246c0faa 100644
--- a/lib/spack/docs/packaging_guide.rst
+++ b/lib/spack/docs/packaging_guide.rst
@@ -4167,16 +4167,23 @@ want to clean up the temporary directory, or if the package isn't
downloading properly, you might want to run *only* the ``fetch`` stage
of the build.
+Spack performs best-effort installation of package dependencies by default,
+which means it will continue to install as many dependencies as possible
+after detecting failures. If you are trying to install a package with a
+lot of dependencies where one or more may fail to build, you might want to
+try the ``--fail-fast`` option to stop the installation process on the first
+failure.
+
A typical package workflow might look like this:
.. code-block:: console
$ spack edit mypackage
- $ spack install mypackage
+ $ spack install --fail-fast mypackage
... build breaks! ...
$ spack clean mypackage
$ spack edit mypackage
- $ spack install mypackage
+ $ spack install --fail-fast mypackage
... repeat clean/install until install works ...
Below are some commands that will allow you some finer-grained