Clear up a bit of modules/dotkit confusion (#8650)

`use` is an overloaded word between dotkit, modules and spack.  Add additional words to make the distinction clear in the docs.
This commit is contained in:
George Hartzell 2018-07-06 10:06:53 -07:00 committed by Adam J. Stewart
parent cf140b5f4c
commit 7f814971a5

View File

@ -113,8 +113,10 @@ Modules Dotkit
========================= ========================== ========================= ==========================
And you can use the same shortened names you use everywhere else in And you can use the same shortened names you use everywhere else in
Spack. For example, this will add the ``mpich`` package built with Spack.
``gcc`` to your path:
For example, if you are using dotkit, this will add the ``mpich``
package built with ``gcc`` to your path:
.. code-block:: console .. code-block:: console
@ -122,16 +124,16 @@ Spack. For example, this will add the ``mpich`` package built with
# ... wait for install ... # ... wait for install ...
$ spack use mpich %gcc@4.4.7 $ spack use mpich %gcc@4.4.7 # dotkit
Prepending: mpich@3.0.4%gcc@4.4.7 (ok) Prepending: mpich@3.0.4%gcc@4.4.7 (ok)
$ which mpicc $ which mpicc
~/spack/opt/linux-debian7-x86_64/gcc@4.4.7/mpich@3.0.4/bin/mpicc ~/spack/opt/linux-debian7-x86_64/gcc@4.4.7/mpich@3.0.4/bin/mpicc
Or, similarly with modules, you could type: Or, similarly if you are using modules, you could type:
.. code-block:: console .. code-block:: console
$ spack load mpich %gcc@4.4.7 $ spack load mpich %gcc@4.4.7 # modules
These commands will add appropriate directories to your ``PATH``, These commands will add appropriate directories to your ``PATH``,
``MANPATH``, ``CPATH``, and ``LD_LIBRARY_PATH``. When you no longer ``MANPATH``, ``CPATH``, and ``LD_LIBRARY_PATH``. When you no longer