More environments corrections, especially to reproducible outputs (#132)

outputs/environments/add-anonymous-1.out

@@ -8,5 +8,9 @@ $ cat spack.yaml
 # configuration settings.
 spack:
   # add package specs to the `specs` list
-  specs: [boost, trilinos, openmpi, hdf5@5.5.1]
+  specs:
+  - boost
+  - trilinos
+  - openmpi
+  - hdf5@5.5.1
   view: true

outputs/environments/find-env-abstract-1.out

@@ -1,4 +1,7 @@
+$ spacktivate abstract
 $ spack find
 ==> In environment abstract
-==> No root specs
+==> Root specs
+boost   openmpi   trilinos 
+
 ==> 0 installed packages

outputs/environments/find-env-concrete-1.out

@@ -0,0 +1,22 @@
+$ spacktivate concrete
+$ spack find
+==> In environment concrete
+==> Root specs
+boost   openmpi   trilinos
+
+==> 40 installed packages
+-- linux-ubuntu18.04-x86_64 / gcc@7.5.0 -------------------------
+autoconf@2.69                libiconv@1.16           openblas@0.3.12
+autoconf-archive@2019.01.06  libpciaccess@0.16       openmpi@3.1.6
+automake@1.16.2              libsigsegv@2.12         openssl@1.1.1h
+berkeley-db@18.1.40          libtool@2.4.6           parmetis@4.0.3
+boost@1.74.0                 libxml2@2.9.10          perl@5.32.0
+bzip2@1.0.8                  m4@1.4.18               pkgconf@1.7.3
+cmake@3.18.4                 matio@1.5.17            readline@8.0
+diffutils@3.7                metis@5.1.0             suite-sparse@5.8.1
+gdbm@1.18.1                  mpfr@4.0.2              trilinos@13.0.1
+glm@0.9.7.1                  mumps@5.3.3             util-macros@1.19.1
+gmp@6.1.2                    ncurses@6.2             xz@5.2.5
+hdf5@1.10.7                  netcdf-c@4.7.4          zlib@1.2.11
+hwloc@1.11.11                netlib-scalapack@2.1.0
+hypre@2.20.0                 numactl@2.0.14

tutorial_environments.rst

@@ -377,7 +377,7 @@ is just a ``spack:`` header and a list of the **root** ``specs``.
    is set to the path of your preferred text editor.
 
 Let's edit this file to *prefer* ``mpich`` as our ``mpi`` provider
-using ``spack edit config``.
+using ``spack config edit``.
 
 You should now have the above file open in your editor. Change it
 to include the ``packages:all:providers:mpi:`` entry below:
@@ -418,16 +418,10 @@ Let's see the effects of this change on our package using ``spack spec``:
 Notice ``mpich`` is now the ``mpi`` dependency for our concretized
 spec. We also see all of its concrete dependencies.
 
-At this point we only wanted to change the default ``mpi`` provider
-for packages that depend on ``mpi``. An environment can contain
-many other types of configuration, such as adding custom package
-repositories and customizing the installation location, compilers,
-and external packages (see :ref:`configuration section <configs-tutorial>`
-for more). Combinatorial environments can be defined (see
-:ref:`stacks <stacks-tutorial>`). Workflows for CI and software
-development, as described in the :ref:`developer workflows
-<developer-workflows-tutorial>` tutorial, can also be configured.
-More links are provided at the end of this tutorial section.
+We've only scratched the surface here by changing the default of
+the ``mpi`` provider for packages depending on ``mpi``. There
+are many other customizations you can make to an environment.
+Refer to the links at the end of this section for more information.
 
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 Reconcretizing the environment
@@ -566,16 +560,16 @@ The two files represent two fundamental concepts:
 * ``spack.lock``: all fully *concrete* specs.
 
 
-You can think of environments as generalizations of specs for sets of
-packages, one abstract and the other concrete.
-
-Both environment files can be versioned in repositories, shared, and
-used to install the same set of software on different machines.
-
 These files are intended to be used by developers and administrators
 to manage the environments in a reproducible way. We will cover their
 re-use later.
 
+.. note::
+
+   Both environment files can be versioned in repositories, shared, and
+   used to install the same set of software by different users and on
+   other machines.
+
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 Managed versus independent environments
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -701,6 +695,7 @@ should now contain the following entries:
      - boost
      - trilinos
      - openmpi
+     view: true
 
 Now activate the environment and install the packages:
 
@@ -722,7 +717,7 @@ Spack supports tweaking an environment even after the initial specs
 are installed. You are free to add and remove specs just as you would
 outside of the environment using the command line interface as before.
 
-For example, lets add ``hdf5`` and look at our file:
+For example, let's add ``hdf5`` and look at our file:
 
 .. literalinclude:: outputs/environments/add-anonymous-1.out
    :language: console
@@ -734,11 +729,11 @@ it appears in the configuration file's spec list.
 
 .. note::
 
-   `spack add` does not install the package in your environment.
-   You'll need to run ``spack install`` for that.
-
+   You'll need to run ``spack install`` to install added packages
+   in your environment because ``spack add`` only adds it to the
+   configuraton.
 
-Now use ``spack remove`` to remove it from the environment:
+Now use ``spack remove`` to remove the spec from the configuration:
 
 .. literalinclude:: outputs/environments/remove-anonymous-1.out
    :language: console
@@ -815,12 +810,15 @@ Here we see that Spack created a managed environment with the name
 we provided.
 
 And, since it is a newly created environment, it does not have any
-specs yet as we can see from calling ``spack find``:
+*installed* specs yet as we can see from calling ``spack find``
+**after** activating the environment:
 
 .. literalinclude:: outputs/environments/find-env-abstract-1.out
    :language: console
-   :emphasize-lines: 1
+   :emphasize-lines: 1-2
 
+Notice we have the same root specs as were listed in the ``spack.yaml``
+file.
 
 """"""""""""""""""""
 Using ``spack.lock``
@@ -831,14 +829,23 @@ original build. It can replicate the build because it contains the
 information for all the decisions made during concretization.
 
 Now let's create a concrete environment, called ``concrete``, from
-the file:
+the file again **after** activating the environment:
 
 .. literalinclude:: outputs/environments/create-from-file-2.out
    :language: console
-   :emphasize-lines: 1
+   :emphasize-lines: 1-2
 
 Here we see that Spack again created a managed environment with the
-provided name. It will also be empty of specs until we add them.
+provided name.
+
+Since we created the environment from our ``spack.lock`` file,
+not only do we get the same root specs, all of the packages are 
+also installed in the environment as we can see from calling
+``spack find`` **after** activating the environment:
+
+.. literalinclude:: outputs/environments/find-env-concrete-1.out
+   :language: console
+   :emphasize-lines: 1-2
 
 .. note::
 
@@ -864,7 +871,7 @@ Setting up and building environments
 * `Spack stacks tutorial
   <https://spack-tutorial.readthedocs.io/en/latest/tutorial_stacks.html>`_:
   for configuring combinatorial environments (e.g., same packages across a
-  range of compilers)
+  list of compilers)
 * `Install-level parallel builds
   <https://spack.readthedocs.io/en/latest/packaging_guide.html#install-level-build-parallelism>`_:
   for how to launch ``spack install`` to build your environment in parallel