summaryrefslogtreecommitdiff
path: root/lib
diff options
context:
space:
mode:
authorGeorge Hartzell <hartzell@alerce.com>2016-07-14 08:31:07 -0700
committerGitHub <noreply@github.com>2016-07-14 08:31:07 -0700
commit3051c3d71d9d7bf0422d2b33a173e5db1ec42ab3 (patch)
tree32e45c3515b652b4a2affa42e98b4aee22cb2375 /lib
parentd24c11f2b10a180316168f2078f9ba1bfeb5bb23 (diff)
downloadspack-3051c3d71d9d7bf0422d2b33a173e5db1ec42ab3.tar.gz
spack-3051c3d71d9d7bf0422d2b33a173e5db1ec42ab3.tar.bz2
spack-3051c3d71d9d7bf0422d2b33a173e5db1ec42ab3.tar.xz
spack-3051c3d71d9d7bf0422d2b33a173e5db1ec42ab3.zip
Fix format of explanation of an example & question
This list was not formatted correctly on [the ReadTheDocs site](http://software.llnl.gov/spack/basic_usage.html#specs-dependencies). I'm not a .rst expert, but I think that it was improperly indented. The example includes an `arch=...` string but *arch* is not listed in the valid compiler flag specifiers or architecture specifiers. Should it be, or is it considered an "optional variant specifier?
Diffstat (limited to 'lib')
-rw-r--r--lib/spack/docs/basic_usage.rst7
1 files changed, 4 insertions, 3 deletions
diff --git a/lib/spack/docs/basic_usage.rst b/lib/spack/docs/basic_usage.rst
index dbad0a9f6d..44052ddbe8 100644
--- a/lib/spack/docs/basic_usage.rst
+++ b/lib/spack/docs/basic_usage.rst
@@ -543,11 +543,12 @@ More formally, a spec consists of the following pieces:
* ``+`` or ``-`` or ``~`` Optional variant specifiers (``+debug``,
``-qt``, or ``~qt``) for boolean variants
* ``name=<value>`` Optional variant specifiers that are not restricted to
-boolean variants
+ boolean variants
* ``name=<value>`` Optional compiler flag specifiers. Valid flag names are
-``cflags``, ``cxxflags``, ``fflags``, ``cppflags``, ``ldflags``, and ``ldlibs``.
+ ``cflags``, ``cxxflags``, ``fflags``, ``cppflags``, ``ldflags``, and ``ldlibs``.
* ``target=<value> os=<value>`` Optional architecture specifier
-(``target=haswell os=CNL10``) * ``^`` Dependency specs (``^callpath@1.1``)
+ (``target=haswell os=CNL10``)
+* ``^`` Dependency specs (``^callpath@1.1``)
There are two things to notice here. The first is that specs are
recursively defined. That is, each dependency after ``^`` is a spec