Telcon: 2023 03 01

Held Wednesday March 1st, 9am PT

Attendees

• Peter Scheibel (host)
• Davide DelVento
• Dom Heinzeller
• Mark Krentel
• Massimiliano Culpo
• Phil Regier
• Richarda Butler
• Srinath Vadlamani
• Tammy Dahlgren
• Wileam Phan

Agenda

• Davide: have a set of modules generated by Spack with manual edits
  • If I reinstall the package I want the module changes to be minimized
  • Massimiliano: see lmod.py
  • Want to replace code like prepend_path(MANPATH, join(prefix_a, 'bin/') rather than prepend_path('prefix_a/bin') (i.e. you define the prefixes at the top as variables
  • See also: https://spack-tutorial.readthedocs.io/en/latest/tutorial_modules.html#add-custom-environment-modifications
    • In other words, if your manual modifications are limited to things like setting env variables, then you can "invert" the process: you can configure spack to generate your modules with the custom per-package edits
• Davide: have a spack installation pinned to a particular spack commit and have installed many packages; I want to replicate that on some new spack
  • Massimilano: environments useful for this
  • Secondary concern: don't want to git pull into my production spack instance, I want to try spack in a new prefix without affecting the other
    • For that set SPACK_USER_CACHE_PATH=… and SPACK_DISABLE_LOCAL_CONFIG=true
  • Overall
    • Clone a new spack
    • copy over the spack.yaml files from the old spack
    • create spack environments with those files in the new spack