Skip to content
Peter Scheibel edited this page Feb 7, 2023 · 23 revisions

Held Wednesday February 1st, 9am PT

Attendees

  • Peter Scheibel (host)
  • Tammy Dahlgren
  • Justin Cook (NERSC)
  • Mark Krentel
  • Massimiliano Culpo
  • Chris Green
  • Sean Koyama
  • Srinath Vadlamani
  • Richarda Butler
  • Greg Becker
  • Todd Gamblin

Agenda

  • Chris: have spack install --only=dependencies in an environment; want to not install any of the roots
    • In particular "root" here means the user specs in the environment
    • Note that is conceptually different from "roots" in an environment (but either way we don't currently have an option etc. for excluding multiple roots from the install)
    • Chris: furthermore, if one root depends on another root, I don't want either root to be installed (this may not work now)
    • Max: how would you do this in an environment which says the roots are hdf5 and zlib
      • For Chris' use case, it would be the intent of the user to install nothing
    • Tammy: Harmen has a PR which is working in the same area (i.e., spack install in environments): #35206
  • Srinath: is there a document on the prototyping of compilers as dependencies
  • Sean (ALCF): how are external modules handled at runtime?
    • Spack loads these modules at build time
    • When using spack load, the associated modules are not loaded
    • The generated module files also do not refer to it
    • We should update spack load to add an option to load the associated modules
    • Sean: of more interest is the generated env modules
Clone this wiki locally