Skip to content
Peter Scheibel edited this page Apr 25, 2022 · 6 revisions

Attendees

  • Peter Scheibel (host)
  • Greg Becker
  • Massimiliano Culpo
  • Phil Regier
  • Brian Van Essen

Agenda items

  • (Peter) We seem to be planning for package.py files to be missing, why?
    • (Greg) For users to provide proprietary software (provided in a binary mirror)
    • (Massimiliano) If a user has their own repository with their own custom version of a package; they submit a PR and it is accepted; they pull the latest Spack and delete the package from their custom repo
    • See: https://github.com/spack/spack/pull/30191
    • We covered a few issues here during discussion:
      • Packages have logic like .libs, .headers, setup_dependent_package... that may be necessary
      • It was suggested these could be cached:
        • That would work in general for .libs except for parameterized versions of it (e.g. hdf5)
        • Not sure how that would work for functions like setup_dependent_package
  • (Greg) Improving error messages for new concretizer
    • Has a test branch: error messages are largely improved except for version constraints (and possibly still complex for all cardinality constraints)
    • This possibly won't be as complete as desired by 0.18, but a partial fix may be ideal to include as part of the 0.18 release

Possible Agenda items

Clone this wiki locally