InterGenOS corresponding source — libSM 1.2.6-1

This archive is the complete corresponding source for the binary package
libSM-1.2.6-1.igos.tar.gz as distributed at
https://repo.intergenos.org/.

CONTENTS
  libSM-1.2.6.tar.xz          every source input package.yml declares
                              (one per declared entry, not only the first)
  libSM-1.2.6.tar.xz.sha256   the SHA256 recorded for that input, one file
                              per tarball, sha256sum -c compatible
  build.sh                    the build script — the recipe's phases as run
  package.yml                 package metadata: version, declared source
                              inputs with their SHA256 pins, dependencies,
                              and installed-file declarations
  README.SOURCES              this file

VERIFYING THIS ARCHIVE
  1. This archive's own SHA256 is recorded in the signed package index
     (InterGenOS.db, signature InterGenOS.db.sig) alongside the binary
     archive's hash — one signature covers both.
  2. Each upstream tarball here can be checked with
     `sha256sum -c <upstream-tarball>.sha256`; the same value is pinned in
     package.yml's source entry.

REPRODUCING THE BINARY
  The binary was produced by the InterGenOS build system from exactly these
  inputs, inside the InterGenOS build environment:
  1. Obtain the InterGenOS source tree at the release this package was cut
     from: https://github.com/InterGenJLU/intergenos — it provides the
     build orchestrator and the build-environment definitions.
  2. Stage the upstream tarball(s) from this archive into build/sources/.
  3. Build the package with the tree's builder — the build.sh and
     package.yml in this archive are the recipe the tree carries at that
     release. Python-tier packages:
         python3 igos-build.py --build --tracked --only libSM \
             --sources-dir <sources-path>
     Bash-tier (core/base) packages build through the tree's
     scripts/chroot-build-<tier>.sh driver, which runs the same build.sh.
  4. The toolchain that compiled the shipped binary is itself distributed
     as InterGenOS packages under this same corresponding-source policy;
     building inside the InterGenOS build chroot (docs/operations/ in the
     source tree) reproduces the shipped configuration.
