diff options
author | Eric Berquist <eric.berquist@gmail.com> | 2023-05-05 18:08:58 -0400 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-05-05 22:08:58 +0000 |
commit | b2a8e8734ef448a2c72f587fc1777e92019cb150 (patch) | |
tree | a312e12b052b3c18401a68aa09724bd09f4c1c23 | |
parent | c287dbbf1327bbeddd5d387b5a88503d92d0828f (diff) | |
download | spack-b2a8e8734ef448a2c72f587fc1777e92019cb150.tar.gz spack-b2a8e8734ef448a2c72f587fc1777e92019cb150.tar.bz2 spack-b2a8e8734ef448a2c72f587fc1777e92019cb150.tar.xz spack-b2a8e8734ef448a2c72f587fc1777e92019cb150.zip |
Fix typos in packaging guide (#37460)
-rw-r--r-- | lib/spack/docs/packaging_guide.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/lib/spack/docs/packaging_guide.rst b/lib/spack/docs/packaging_guide.rst index 969da6de20..b6ab8f7230 100644 --- a/lib/spack/docs/packaging_guide.rst +++ b/lib/spack/docs/packaging_guide.rst @@ -2971,7 +2971,7 @@ appears as follows: baz/lib/libFooBaz.so The install tree shows that ``foo`` is providing the header ``include/foo.h`` -and library ``lib64/libFoo.so`` in it's install prefix. The virtual +and library ``lib64/libFoo.so`` in its install prefix. The virtual package ``bar`` is providing ``include/bar/bar.h`` and library ``lib64/libFooBar.so``, also in ``foo``'s install prefix. The ``baz`` package, however, is provided in the ``baz`` subdirectory of ``foo``'s @@ -3455,7 +3455,7 @@ the build system. The build systems currently supported by Spack are: | | licensed Intel software | +----------------------------------------------------------+----------------------------------+ | :class:`~spack.build_systems.oneapi` | Specialized build system for | -| | Intel onaAPI software | +| | Intel oneAPI software | +----------------------------------------------------------+----------------------------------+ | :class:`~spack.build_systems.aspell_dict` | Specialized build system for | | | Aspell dictionaries | @@ -5957,7 +5957,7 @@ location of a dependency. The difference is that while ``prefix`` is the location on disk where a concrete package resides, ``home`` is the `logical` location that a package resides, which may be different than ``prefix`` in the case of virtual packages or other special circumstances. For most use -cases inside a package, it's dependency locations can be accessed via either +cases inside a package, its dependency locations can be accessed via either ``self.spec["foo"].home`` or ``self.spec["foo"].prefix``. Specific packages that should be consumed by dependents via ``.home`` instead of ``.prefix`` should be noted in their respective documentation. |