Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .gitmodules
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
[submodule "_spack_root"]
path = _spack_root
url = https://github.com/spack/spack.git
branch = releases/v1.0
branch = releases/v1.2
[submodule "_spack_packages"]
path = _spack_packages
url = https://github.com/spack/spack-packages
branch = releases/v2025.07
branch = releases/v2026.06
2 changes: 1 addition & 1 deletion _spack_root
Submodule _spack_root updated 720 files
34 changes: 16 additions & 18 deletions tutorial_configuration.rst
Original file line number Diff line number Diff line change
Expand Up @@ -142,13 +142,13 @@ For example, look at high-level config:

--- config:
/etc/spack/config.yaml:2 suppress_gpg_warnings: True
/home/spack/spack/etc/spack/defaults/config.yaml:19 install_tree:
/home/spack/spack/etc/spack/defaults/config.yaml:20 root: $spack/opt/spack
/home/spack/spack/etc/spack/defaults/base/config.yaml:19 install_tree:
/home/spack/spack/etc/spack/defaults/base/config.yaml:20 root: $spack/opt/spack
...
/home/spack/spack/etc/spack/defaults/config.yaml:238 aliases:
/home/spack/spack/etc/spack/defaults/config.yaml:239 concretise: concretize
/home/spack/spack/etc/spack/defaults/config.yaml:240 containerise: containerize
/home/spack/spack/etc/spack/defaults/config.yaml:241 rm: remove
/home/spack/spack/etc/spack/defaults/base/config.yaml:238 aliases:
/home/spack/spack/etc/spack/defaults/base/config.yaml:239 concretise: concretize
/home/spack/spack/etc/spack/defaults/base/config.yaml:240 containerise: containerize
/home/spack/spack/etc/spack/defaults/base/config.yaml:241 rm: remove


We can see overrides in action with:
Expand Down Expand Up @@ -601,10 +601,10 @@ You can see the default settings by running:

.. code-block:: console

$ spack config --scope defaults edit config
$ spack config --scope defaults:base edit config


.. literalinclude:: _spack_root/etc/spack/defaults/config.yaml
.. literalinclude:: _spack_root/etc/spack/defaults/base/config.yaml
:language: yaml


Expand All @@ -627,18 +627,15 @@ If you have a fast scratch file system, you can run builds from this file system
See `Basic Settings <https://spack.readthedocs.io/en/latest/config_yaml.html#config-yaml>`_ for details.


On systems with compilers that absolutely *require* environment variables like ``LD_LIBRARY_PATH``, it is possible to prevent Spack from cleaning the build environment with the ``dirty`` setting:

.. code-block:: yaml
One last setting that may be of interest to many users is the ability to customize the parallelism of Spack builds.
By default, Spack installs all packages in parallel with the number of jobs equal to the number of cores on the node.

config:
dirty: true
This is easier to demonstrate using the old installer's output, so we'll switch to that for this example.

.. code-block:: console

However, this is strongly discouraged, as it can pull unwanted libraries into the build.
$ spack config add config:installer:old

One last setting that may be of interest to many users is the ability to customize the parallelism of Spack builds.
By default, Spack installs all packages in parallel with the number of jobs equal to the number of cores on the node.
For example, on a node with 16 cores, this will look like:

.. code-block:: spec
Expand Down Expand Up @@ -689,15 +686,16 @@ If we uninstall and reinstall zlib, we see that it now uses only 2 cores:

Obviously, if you want to build everything in serial for whatever reason, you would set ``build_jobs`` to 1.

Last, we'll unset ``concretizer:reuse:false`` since we'll want to enable concretizer reuse for the rest of this tutorial.
Last, we'll unset ``concretizer:reuse:false`` and ``config:installer:old`` since we'll want to enable concretizer reuse and the terminal user interface for the rest of this tutorial.

.. code-block:: console

$ spack config rm concretizer:reuse
$ spack config rm config:installer

.. warning::

If you do not do this step, the rest of the tutorial will not reuse binaries!
If you do not do this step, the rest of the tutorial will not reuse binaries or use the TUI!

----------
Conclusion
Expand Down
2 changes: 1 addition & 1 deletion tutorial_modules.rst
Original file line number Diff line number Diff line change
Expand Up @@ -848,7 +848,7 @@ The rest of the file is then divided into `blocks <http://jinja.pocoo.org/docs/2

The locations where Spack looks for templates are specified in ``config.yaml``:

.. literalinclude:: _spack_root/etc/spack/defaults/config.yaml
.. literalinclude:: _spack_root/etc/spack/defaults/base/config.yaml
:language: yaml
:lines: 32-35

Expand Down
Loading