Telcon: 2021 09 22

Attendees

• Todd Gamblin
• Greg Becker
• Peter Scheibel
• (TBD)

Agenda

• (TBC from last week) Discussion: Packages which require multiple build systems: how to handle them?

  • Discussions on this:
    • (Proposal based on using a new directive) https://github.com/spack/seps/blob/8dafadb4cae08275d168af964b3d168b4248977f/seps/sep-0002.md
    • (Notes on trying an approach based on a when class decorator) https://github.com/spack/seps/issues/4
  • Two approaches were covered: Greg thought there were issues with both; we will cover that next week.

• Discussion: Packages with multiple conflicting libraries - how to support them?

  • For now, any such package installed by Spack advertises just one from the set (this ensures that everything is consistent where needed)
  • https://github.com/spack/seps/pull/2
  • Brian: opencv will try to install its own openblas (which may conflict with what Spack chooses)
    • Mvapich2 installs its own hwloc
    • (Peter) I think this is a separate but still interesting problem.

• (For next week) What about packages that install some other package with them

  • E.g. Mvapich2 installs hwloc with it
  • Would it be good to allow a Spack package to describe these additional packages that "come along" with it

• Discussion: long environment activations - are you having an issue with this?

  • Some large envs might have this problem, e.g.: https://github.com/spack/spack/issues/25555

• Harmen Stoppels

  • Only load root specs in an environment: https://github.com/spack/spack/pull/25755
  • Remove setup_dependent_run_environment in favor of setup_run_environment: https://github.com/spack/spack/pull/26031
  • Should spack load x be roughly equivalent to spack env activate y with x as root spec? https://github.com/spack/spack/pull/25732 spack load needs some love