Skip to content

docs: when EasyBuild alone is enough, and which tools call eb-stack - #56

Merged
HaoZeke merged 1 commit into
mainfrom
docs/when-easybuild-is-enough
Nov 18, 2026
Merged

HaoZeke merged 1 commit into
mainfrom
docs/when-easybuild-is-enough

Conversation

@HaoZeke

@HaoZeke HaoZeke commented Nov 18, 2026

Copy link
Copy Markdown
Collaborator

A section after the opening names the EasyBuild options that cover one recipe or one build list (--try-software-version, --try-update-deps, --inject-checksums, --robot with --dry-run or --missing-modules, --easystack, --from-pr) and EESSI's easystack-and-bot route, then what eb-stack adds and which stackhands tool calls each verb: stack admit (eb-pipeline), stack arch (eessi-arch-guard --check-submit), stack gap --site (eb-keep-logs usage --active), ledger (eb-staged-rebuild). The release line no longer says 0.7.4 carries commands the changelog lists as unreleased. Also syncs the stackhands table.

Name the EasyBuild options that cover one recipe or one list (try-*,
inject-checksums, robot with dry-run or missing-modules, easystack,
from-pr), then what eb-stack adds and which stackhands tool calls each
verb: stack admit (eb-pipeline), stack arch (eessi-arch-guard), stack
gap --site (eb-keep-logs usage), ledger (eb-staged-rebuild).
@HaoZeke
HaoZeke merged commit d0ed0bd into main Nov 18, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant