Skip to content

Telcon: 2021 10 13

Jump to bottom Edit New page
Peter Scheibel edited this page Oct 13, 2021 · 24 revisions

Attendees

  • Peter Scheibel
  • Mark Krentel
  • Gregory Becker
  • Kayla Butler
  • Massimiliano Culpo
  • Phil Sakievich
  • Richard Henwood
  • Tammy Dahlgren
  • Srinath Vadlamani
  • Nick Sly

Agenda

  • (For next week) Mark Krentel: issues with Clingo concretization. In particular with virtuals.

    • Currently in slack, not github
    • Greg: virtual versions are not properly forwarded to provider versions

  • Greg/Harmen: versions https://github.com/spack/spack/discussions/26557

    • Peter: what about foo<4 string conversion to foo@:3.999?
    • Greg: what about "foo@3.*" ("I want any version 3")?
    • Harmen: what about foo@=3 ("I want exactly version 3, even if there's a 3.0")?
      • Greg: each time you use a compiler with different fortrans but the same compiler
      • %appleclang@11.0.0-gfortran
      • %appleclang@11.0.0
      • Spack treats compiler versions as exact but not package versions
    • Greg: why not have foo@3 mean "exactly 3"?
      • And then users who want 3.x can ask for foo<4

  • Phil Sakievich: spack develop questions about direction

  • Peter: when is the user scope necessary?

    • I've asserted we need it in some cases
    • For shared filesystems, it can be very annoying though, so I'd like to figure out if it could in fact be removed entirely
    • If using spack without an env, then there's a question of where to write config data to
      • ~ is an obvious choice
      • There is also a PR which introduces an install-tree scope, which would be owned by the user

  • Tammy: should we build (and retain) the test dependencies at concretization/build time, especially if --test is used?

    • If not, there a potential issue with inconsistent test dependencies used to run tests at build time versus those used for stand-alone tests.
      • This has been observed with dependencies such as CMake (versions).
    • TBC next week
    • If you concretize at test time (vs. build time) then this depends on reuse in the concretizer

  • Discussion: Packages which require multiple build systems: how to handle them?

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

  • Discussion: what does it mean to set a preferred variant in packages.yaml?

Add a custom footer
Clone this wiki locally