Site R extras on EESSI¶
Turn a Comprehensive R Archive Network (CRAN) DESCRIPTION, CRAN JSON object, or package list into a
Bundle easyconfig with exts_defaultclass = 'RPackage'. Base-R
packages (methods, utils, …) are dropped. R (>= x) becomes a
dependency on the EasyBuild R module. Packages already listed in
R-bundle-CRAN exts_list are satisfied as provides.
Inputs¶
a DESCRIPTION file,
cran.json, or a one-spec-per-line package list;the European Environment for Scientific Software Installations (EESSI) robot tree, passed as
--easyconfigs. It is the easyconfigs directory bundled with EESSI’s EasyBuild:$EBROOTEASYBUILD/easybuild/easyconfigsafter loading EESSI’sEasyBuildmodule;a stack policy that locks
RandR-bundle-CRANto the versions in the robot. Seeexamples/stacks/eessi-r-extras.toml.
Inspect¶
eb-stack package inspect \
--source fixtures/foreign_ingest/cran_jsonlite/DESCRIPTION \
--format cran \
--toolchain foss/2026.1 \
--out-dir /tmp/jsonlite-inspect
package.plan.json has origin = cran. A single package, such as
this DESCRIPTION, has easyblock = RPackage, and that field stays
RPackage after planning. The emitted recipe is a Bundle with
exts_defaultclass = 'RPackage' and the package in exts_list.
Base-R imports are residuals (cran-base). A DESCRIPTION with no
digest is a checksum residual.
Plan¶
The fixture robot does not already provide jsonlite, so this command
emits the bundle. The checksum is the placeholder stored with the
fixture. Against easybuild-easyconfigs develop, source env.sh from
scripts/fetch-upstream-trees.sh and pass --easyconfigs "$EB_EASYCONFIGS"
with the archive digest of
jsonlite_1.8.8.tar.gz. That tree already provides the package, so
plan prints the closure and does not emit a recipe.
eb-stack package plan \
--source fixtures/foreign_ingest/cran_jsonlite/cran.json \
--format cran \
--toolchain foss/2026.1 \
--easyconfigs fixtures/foreign_ingest/cran_jsonlite/robot \
--stack-policy examples/stacks/eessi-r-extras.toml \
--source-checksum bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb \
--out-dir /tmp/eb-stack/bundles/jsonlite
The develop run’s manifest residual is:
jsonlite 1.8.8 is already provided by R 4.6.1 (jsonlite 2.0.0); do not emit a pip overlay
The evidence path is r/R/R-4.6.1-gfbf-2026.1.eb. DESCRIPTION files
rarely carry a SHA-256. Pass --source-checksum for the tarball, or use
a JSON document that already includes one. Plan refuses to emit a
buildable bundle without it. When the robot does not already provide
the package, plan emits easyblock = Bundle with
exts_defaultclass = RPackage.
Check the recipe¶
Plan on the host, then confirm the recipe resolves against the same robot:
eb-stack recipe check \
--recipe /tmp/eb-stack/bundles/jsonlite/easyconfigs/j/jsonlite/jsonlite-1.8.8-foss-2026.1.eb \
--easyconfigs fixtures/foreign_ingest/cran_jsonlite/robot \
--easyconfigs /tmp/eb-stack/bundles/jsonlite/easyconfigs
The check prints recipe resolves and finds R-4.4.2 (foss-2026.1).
Project one-offs can keep using R_LIBS_USER instead of a site bundle.
Dependencies that state no version¶
A CRAN package routinely imports another by bare name, with no version at all.
Nothing is wrong with that, but an exts_list entry needs one
concrete version, so planning stops with
processx is not in the robot, and ">=0" names no version to install as an extension. Give the ecosystem index with --package-index, or pin the dependency
That is what this fixture prints:
eb-stack package plan \
--source fixtures/foreign_ingest/cran_unpinned/cran.json \
--format cran \
--toolchain foss/2026.1 \
--easyconfigs fixtures/foreign_ingest/cran_bundle/robot \
--stack-policy examples/stacks/eessi-r-extras.toml \
--source-checksum dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd \
--out-dir /tmp/eb-stack/bundles/quartoish
Give it an index in the control-file shape CRAN publishes. Versions and
MD5sum values for the leftovers come from that file:
cat > /tmp/PACKAGES <<'EOF'
Package: processx
Version: 3.8.4
MD5sum: 1111111111111111111111111111abcd
Package: rmarkdown
Version: 2.27
MD5sum: 2222222222222222222222222222abcd
EOF
eb-stack package plan \
--source fixtures/foreign_ingest/cran_unpinned/cran.json \
--format cran \
--toolchain foss/2026.1 \
--easyconfigs fixtures/foreign_ingest/cran_bundle/robot \
--stack-policy examples/stacks/eessi-r-extras.toml \
--package-index /tmp/PACKAGES \
--source-checksum dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd \
--out-dir /tmp/eb-stack/bundles/quartoish
The index is a control file: stanzas of Field: value separated by blank
lines. Versions for unpinned leftovers come from it, and so do their checksums,
since CRAN publishes an MD5sum per package and EasyBuild accepts a tagged
md5: value. It is a file, so a plan stays reproducible
and works offline against a copy taken at a known time.
Without an index the error above is the right outcome: installing whatever version happens to be current, unrecorded, is worse than stopping.
When this emits a Bundle¶
Inspect records RPackage. Plan emits a Bundle with
exts_defaultclass = 'RPackage' and the package, or its leftovers, in
exts_list. A single package whose imports the robot already carries
still uses that shape, because a lone RPackage recipe has nowhere to
put a later leftover:
easyblock = 'Bundle'
exts_defaultclass = 'RPackage'
exts_list = [
('jsonlite', '1.8.8', {...}),
]
plan_cran_emits_a_single_r_package is jsonlite alone.
plan_cran_with_leftovers_emits_an_r_bundle puts processx and
rmarkdown in the same list. The index plan above writes
('processx', '3.8.4' and the md5: value from the index.
An already-provided import collapses to its provider instead of becoming an
extension, through the same mechanism Python packages use: an R-bundle-CRAN
in the robot tree satisfies a requirement for one of its exts_list entries.