Then the software.

The shopping list that goes with the toolbox below. Once a machine has the foundation from "Generic prefix install", this adds the actual scientific software - compilers, R, Python, the libraries - building each item in order and keeping track of progress, so an interrupted run picks up where it left off instead of starting over.

The software list, and nothing else. Drop it inside a built prefix-install tree and one command builds every easyconfig into it - compilers, toolchain, R, Python, the libraries. It carries no prefix and no EasyBuild installation: prefix-install is the foundation, this is what gets built on top. Two separate repos because the foundation takes hours and is proven once per machine, while the software list changes often - so a new suite never re-delivers a 20 GB prefix, and a working prefix is never rebuilt to pick one up. Resumable per easyconfig; a recipe whose upstream moved is recorded and the run continues.

build-suite.sh easyconfigs manifest README.md run.R

• A prefix-install tree that finished (__STACK_DONE__) - this directory is copied INSIDE it
• Network for the sources each easyconfig declares; nothing else is contacted
• Hours to days for a full suite, and tens of GB - it builds a compiler first
• Heads-up: 13 carried recipes bake an internal package host into their modulefiles (README)

# from R, via the rxedn catalogue
rxedn::rxedn_install_module("eb.extract.ndexr.io")

# the extraction lands at <domains_dir>/eb.extract.ndexr.io/easybuild-suite/

No archive to unpack and no checksum to compare: rxedn publishes each repo as an immutable <host>-<sha7>.tar.gz and records its sha256 in the catalogue index, so the commit is the identity. Pull it, and the files are simply there.

# the foundation first, once - see the prefix-install card
# drop the directory inside the prefix tree built by step 1
cp -r easybuild-suite /opt/prefix-install/
cd /opt/prefix-install/easybuild-suite

# from R (Workbench session) - session-core-aware kickoff:
#   source('run.R'); kickoff(); build_status(); suite_list()

./build-suite.sh --list        # what will build, and what already has
./build-suite.sh               # the whole suite; resumes where it stopped
./build-suite.sh --only R      # or just one thing

Output stays put, in eb/software/ and eb/modules/all/ in the prefix-install tree (module avail) - nothing is copied out.

EasyBuild suite (companion to prefix-install)

Carried in manifest/ , verbatim - the declared set this extraction will build. It travels in the repo, so a copy taken to a machine with no route back here still knows the full list.