zhangyiss/spack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Fix outdated pre-0.18 text on build dependencies (#31860)

Browse Source
This commit is contained in:
Todd Gamblin 2022-08-02 04:34:58 -07:00 committed by GitHub
parent ac3b1d77fb
commit 415ac29665
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
lib/spack/docs/packaging_guide.rst
View File

@ -699,7 +699,7 @@ Spack versions may also be arbitrary non-numeric strings, for example
``@develop``, ``@master``, ``@local``. ``@develop``, ``@master``, ``@local``.
The order on versions is defined as follows. A version string is split The order on versions is defined as follows. A version string is split
into a list of components based on delimiters such as ``.``, ``-`` etc. into a list of components based on delimiters such as ``.``, ``-`` etc.
Lists are then ordered lexicographically, where components are ordered Lists are then ordered lexicographically, where components are ordered
as follows: as follows:
@ -2283,9 +2283,17 @@ The following dependency types are available:
One of the advantages of the ``build`` dependency type is that although the One of the advantages of the ``build`` dependency type is that although the
dependency needs to be installed in order for the package to be built, it dependency needs to be installed in order for the package to be built, it
can be uninstalled without concern afterwards. ``link`` and ``run`` disallow can be uninstalled without concern afterwards. ``link`` and ``run`` disallow
this because uninstalling the dependency would break the package. Another this because uninstalling the dependency would break the package.
consequence of this is that ``build``-only dependencies do not affect the
hash of the package. The same is true for ``test`` dependencies. ``build``, ``link``, and ``run`` dependencies all affect the hash of Spack
packages (along with ``sha256`` sums of patches and archives used to build the
package, and a [canonical hash](https://github.com/spack/spack/pull/28156) of
the ``package.py`` recipes). ``test`` dependencies do not affect the package
hash, as they are only used to construct a test environment *after* building and
installing a given package installation. Older versions of Spack did not include
build dependencies in the hash, but this has been
[fixed](https://github.com/spack/spack/pull/28504) as of [Spack
``v0.18``](https://github.com/spack/spack/releases/tag/v0.18.0)
If the dependency type is not specified, Spack uses a default of If the dependency type is not specified, Spack uses a default of
``('build', 'link')``. This is the common case for compiler languages. ``('build', 'link')``. This is the common case for compiler languages.
@ -3043,7 +3051,7 @@ the above attribute implementations:
[ [
'/opt/spack/linux-fedora35-haswell/gcc-11.3.1/foo-1.0-ca3rczp5omy7dfzoqw4p7oc2yh3u7lt6/baz/lib' '/opt/spack/linux-fedora35-haswell/gcc-11.3.1/foo-1.0-ca3rczp5omy7dfzoqw4p7oc2yh3u7lt6/baz/lib'
] ]
.. _abstract-and-concrete: .. _abstract-and-concrete:
------------------------- -------------------------