Skip to content
Snippets Groups Projects
Select Git revision
  • highfive-mpi
  • master default protected
  • py-onnxruntime-1.21.0
  • v25.10-stable protected
  • pr/spack_env_create
  • pr/trigger_xl_only
  • v25.09-stable protected
  • geant4-vecgeom-cuda
  • target-x86_64_v3
  • py-tensorflow-cuda
  • arm64
  • py-numba
  • github-actions-build-chain
  • wdconinc-master-patch-89061
  • unpin-pip
  • jl
  • acts-svg
  • numpy-unpin
  • view-hardlink
  • gaudi-39.4
  • spack-unpin
  • v25.10.1-stable
  • v25.10.0-stable
  • v25.09.0-stable
  • v25.08.0-stable
  • v25.07.0-stable
  • v25.06.1-stable
  • v25.06.0-stable
  • v25.05.0-stable
  • v25.04.1-stable
  • v25.04.0-stable
  • v25.03.1-stable
  • v25.03.0-stable
  • v25.02.0-stable
  • v25.01.1-stable
  • v25.01.0-stable
  • v24.12.0-stable
  • 24.11.2
  • 24.11.2-stable
  • v24.11.2-stable
  • v24.11.1-stable
41 results

eic_container

EIC Software Environment Container

Installation Instructions

For installation instructions of eic-shell, see https://github.com/eic/eic-shell.

Updating a package

An individual package is updated on spack package repository along with a spack version upgrade

This situation just requires modifying the eic-shell yaml file.

An individual package is updated on spack package repository after a spack version upgrade

This circumstance requires special cherry pick.

Example: !879 (diffs)

In this example, the spack package xrootd had the latest version 5.6.9 which was put in after a spack version upgrade. We had to modify the eic-shell spack.sh file to include the commit hash of the version update from the main spack package repository in addition to modifying the eic-shell yaml file.