Skip to content
Tamara Dahlgren edited this page Jun 19, 2025 · 13 revisions

Wednesday June 18th, 9am PT (UTC -7:00)

Attendees

  • Peter Scheibel (host)
  • Brad Richardson
  • Dom H
  • Diego Menéndez
  • Davide Del Vento
  • Tammy Dahlgren

Agenda

This meeting is for general Q&A. There are no pre-planned topics (feel free to add one).

  • Dom: for new repo in spack packages, what is your approach from the developer side for supporting package PRs
    • ~200 or so PRs open
    • Peter: we intend to continue support (perhaps we need to do some catch-up)
    • Tammy: we're focused on getting v1.0 out so reviewing package PRs are currently on the lower priority side
  • Diego: questions about compiler management in 1.0 (latest develop today)
  • Diego: when I spack find sometimes I see packages with no arch, what are those packages?
    • Peter: maybe things without statements like depends_on(c)?
      • Tammy: might depend on whether the dependency was there when the package was installed as the one shown does currently have depends_on(c).
    • (there's also a no-compilers section though which includes things that don't have a compiler)
  • Brad: the exact right constraints for any package are never known
    • as people update package files to add constraints, things that previously concretized for others and built will be rejected by the concretizer
    • i.e. we installed a list of specs in our env, we pulled package updates, and got a concretizer failure
    • e.g. hdf5 building against openmpi (it stopped building against openmpi pre-4.0, but I just did it before a spack update)
    • some of this is removal of old versions
    • Another case, I originally asked for openmpi@5+legacy_launchers, but that was later forbidden
  • Diego: Difference between "spack install --concurrent-packages" (new) vs. "--jobs" (pre-existing)?
    • Brad: former is about building multiple packages in parallel, latter is about make jobs for building a single package

Clone this wiki locally