Skip to content
Peter Scheibel edited this page Aug 10, 2022 · 36 revisions

(Held August 10th 2022)

Attendees

  • Peter Scheibel (host)
  • Mark Krentel
  • Brian Van Essen
  • Brandon T. Klein
  • Chris Green
  • Davide DelVento
  • Massimiliano Culpo
  • Matt Belhorn [OLCF]
  • Phil Regier
  • Phil Sakievich [SNL]
  • Tammy Dahlgren
  • Wileam Phan

Agenda items

  • Other topics:
    • (Chris) Ideas and issues re automatic generation of recipe trees for Perl modules
      • How to automatically generate package.py for Perl packages
      • CPAN has "modules" and "distributions"; dependencies are attributes of distributions; they specify dependencies on modules
      • xutils makemaker consists of many modules
      • Other perl modules might depend on the individual files in a distributions
      • Different Perl distributions may provide the same package
        • How does Perl address this?
        • It has a notion of "provides"
      • Are many of these "pure" Perl modules?
        • Yes but many are also not
      • Does Python have a notion of "private" dependencies? i.e. if you install a Python binary package can it have it's own private versions of dependencies?
    • (Phil) how to handle SSL verification (this might be interfering with bootstrapping, i.e. if SSL configuration is causing problems)
      • (in particular if Spack uses its own curl)
      • (Matt) in our case we always use an external openssl
      • Should external find be more-aggressive with getting curl/openssl
      • (Chris) some external openssl packages are kept up to date, but not compatible with Python 3.10
      • (Phil) for basic functionality in Spack, we want to maximize "out-of-the-box" functionality
      • (Brandon) Enterprise will have a proxy/reverse-proxy (like squid)
        • And also packet inspection
        • And also potentially a custom cert bundle
        • Could we tell Spack to use a custom SSL cert path
        • And OpenJDK, Yarn, Git, NPM (i.e. there are several packages which trip over custom certs)
      • Does external openssl work?
        • Generally yes: but e.g. rust needs a newer one
      • You can also install openssl certs=system
        • Should spack bootstrap prefer this?
        • We might need to be careful about custom certs while bootstrapping
      • (Massimiliano) can you use spack bootstrap mirror?
        • This creates a mirror with everything needed for bootstrap
        • You can then move that to anywhere that you cannot download
      • We should allow updating config.yaml with a cacerts location that urllib will use when downloading files
      • "certify" library

Next week

  • Davide: if I have a production install of Spack at 0.18, and I want to update Spack to 0.18.1, what do I need to be careful about?
  • (Chris) Options for spack style checking of user package repos (see https://github.com/spack/spack/pull/31938).
  • (Brian) Sanitizing repo, getting rid of improperly-concretized packages (i.e. how do I get rid of old stuff I don't use now)
    • (in particular reuse)
  • (Mark) Ping on #27247
  • (Matt) Package reuse is nice, but how can we refresh a single package?
    • E.g. want to use the newest version of spectrum-mpi
  • (Matt) How does spack deprecate handle refreshing module files for packages that depend on a deprecated spec in an lmod hierarchy?
    • e.g. if you deprecate the old MPI, does the lmod refresh use the newer MPI in the hierarchy
  • (Davide) Ping on spec comparisons
  • (Davide) Desire to duplicate an installation
    • The environment will not concretize the same time if you copy the spack.yaml
    • Is the spack.lock useful for this?
    • The installation might have many environments (so copying one environment may not address all of it)
    • How to regenerate the lmod hierarchy

Possible Agenda items

Clone this wiki locally