mod accel_install

module accel_install

Classify EasyBuild recipes the way EESSI decides the install prefix.

EESSI’s pre_fetch_hook_check_installation_path (software-layer-scripts eb_hooks.py) calls self.cfg.dependency_names() with no arguments. In EasyBuild 5.4.2 that method defaults to build_only=False, runtime_only=False, which asks dependencies() for builddependencies plus dependencies and then applies --filter-deps. A package is accelerator software when its name is an accelerator runtime, when any remaining (build or runtime) dependency is one, or when its toolchain is an accelerator toolchain. Everything else is CPU-only and must not install into an /accel/ prefix. Classification uses those dependency and toolchain facts — not application package-name lists.

Variables

const ACCELERATOR_DEP_NAMES: &[&str]

Accelerator runtimes EESSI refuses to install outside /accel/.

const ACCELERATOR_TOOLCHAIN_NAMES: &[&str]

Toolchains EESSI treats as accelerator builds even without a direct CUDA or ROCm-LLVM dependency entry.

Functions

fn effective_dependency_names<'a>(candidate: &'a Candidate, filter: &FilterDeps) -> Vec<&'a str>

Direct dependency names EasyBuild 5.4.2 dependency_names() would return for this candidate after --filter-deps: builddependencies and dependencies, with filtered names removed.

fn is_accelerator_candidate(candidate: &Candidate) -> bool

is_accelerator_candidate_filtered with an empty filter list.

fn is_accelerator_candidate_filtered(candidate: &Candidate, filter: &FilterDeps) -> bool

Whether this candidate is accelerator software under EESSI’s install-path check, after applying filter the way dependency_names() does.