You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tutorial_environments.rst
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,12 +52,18 @@ Goals of this Tutorial
52
52
----------------------
53
53
54
54
This tutorial will teach you the fundamentals of creating and using Spack environments.
55
+
55
56
We'll cover:
57
+
56
58
1. Command line basics -- Creating and managing environments with Spack commands.
59
+
57
60
2. Configuration files -- Editing ``spack.yaml`` and understanding ``spack.lock``.
61
+
58
62
3. Environment types -- Understanding Spack-managed vs. independent environments.
63
+
59
64
4. Reproducible builds -- Sharing and recreating environments across systems.
60
65
66
+
61
67
-------------------
62
68
Environment Basics
63
69
-------------------
@@ -371,9 +377,9 @@ We can also add and install specs to an environment incrementally. For example:
371
377
If we create environments incrementally, Spack ensures that already installed roots are not re-concretized.
372
378
So, adding specs to an environment at a later point in time will not cause existing packages to rebuild.
373
379
374
-
Adding and installing specs incrementally leads to greedy concretization, meaning that the environment may concain different package versions compared to an environment created all at once.
380
+
Adding and installing specs incrementally leads to greedy concretization, meaning that the environment may have different package versions compared to an environment created all at once.
375
381
376
-
When you first install ``python`` in an environment, Spack will pick a recent version for it.
382
+
When you first install ``python`` in an environment, Spack will pick a recent version.
377
383
If you then add ``py-numpy``, it may be in conflict with the ``python`` version already installed, and fail to concretize:
0 commit comments