From d6274e1a1d82593d854ef7ba77c260257086f458 Mon Sep 17 00:00:00 2001 From: William F Godoy Date: Wed, 13 Nov 2019 16:21:27 -0500 Subject: Docs update for deprecated `spack sha256` (#13701) * Docs update for deprecated `spack sha256` * Added macOS shasum * Update lib/spack/docs/packaging_guide.rst Co-Authored-By: Adam J. Stewart --- lib/spack/docs/packaging_guide.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'lib') diff --git a/lib/spack/docs/packaging_guide.rst b/lib/spack/docs/packaging_guide.rst index 767a744baa..1759e8c824 100644 --- a/lib/spack/docs/packaging_guide.rst +++ b/lib/spack/docs/packaging_guide.rst @@ -1464,8 +1464,8 @@ that the same package with different patches applied will have different hash identifiers. To ensure that the hashing scheme is consistent, you must use a ``sha256`` checksum for the patch. Patches will be fetched from their URLs, checked, and applied to your source code. You can use -the ``spack sha256`` command to generate a checksum for a patch file or -URL. +the GNU utils ``sha256sum`` or the macOS ``shasum -a 256`` commands to +generate a checksum for a patch file. Spack can also handle compressed patches. If you use these, Spack needs a little more help. Specifically, it needs *two* checksums: the -- cgit v1.2.3-70-g09d2