diff options
| -rw-r--r-- | lib/spack/docs/packaging_guide.rst | 14 |
1 files changed, 10 insertions, 4 deletions
diff --git a/lib/spack/docs/packaging_guide.rst b/lib/spack/docs/packaging_guide.rst index 585276739c..54ad132e10 100644 --- a/lib/spack/docs/packaging_guide.rst +++ b/lib/spack/docs/packaging_guide.rst @@ -4379,10 +4379,16 @@ implementation was selected for this build: elif "mvapich" in spec: configure_args.append("--with-mvapich") -It's also a bit more concise than satisfies. The difference between -the two functions is that ``satisfies()`` tests whether spec -constraints overlap at all, while ``in`` tests whether a spec or any -of its dependencies satisfy the provided spec. +It's also a bit more concise than satisfies. + +.. note:: + + The ``satisfies()`` method tests whether this spec has, at least, all the constraints of the argument spec, + while ``in`` tests whether a spec or any of its dependencies satisfy the provided spec. + + If the provided spec is anonymous (e.g., ":1.2:", "+shared") or has the + same name as the spec being checked, then ``in`` works the same as + ``satisfies()``; however, use of ``satisfies()`` is more intuitive. ^^^^^^^^^^^^^^^^^^^^^^^ Architecture specifiers |