From 0a97da91126d32811b271eb3338aff64582e96ad Mon Sep 17 00:00:00 2001 From: janb84 Date: Wed, 24 Sep 2025 10:29:28 +0200 Subject: [PATCH] guix: documented shasum gathering command --- contrib/guix/README.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/contrib/guix/README.md b/contrib/guix/README.md index 7f6b8232bba..c85c9d40433 100644 --- a/contrib/guix/README.md +++ b/contrib/guix/README.md @@ -103,6 +103,25 @@ worktree to save disk space: ./contrib/guix/guix-clean ``` +## Gathering shasums of build outputs + +After a successful build, the shasums of the build outputs are gathered +into files named `SHA256SUMS`. These files are located in each of the +architecture-specific output directories. + +To gather all shasums and output them together to console, for e.g. +inclusion in a Guix pull request comment, run: + +For branch- or PR-based checkouts, use: +``` sh +uname -m && find guix-build-$(git rev-parse --short=12 HEAD)/output/ -type f -print0 | env LC_ALL=C sort -z | xargs -r0 sha256sum +``` + +For tag-based checkouts, use: +``` sh +uname -m && find guix-build-$(git describe --tags --exact-match | sed 's/^v//')/output/ -type f -print0 | env LC_ALL=C sort -z | xargs -r0 sha256sum +``` + ## Attesting to build outputs