Skip to content

Telcon: 2018 04 19

Jump to bottom Edit New page
scheibelp edited this page Apr 19, 2018 · 21 revisions

Attendees

  • Peter Scheibel (host)
  • Michael Pozulp
  • Patrick Gartung
  • Todd Gamblin
  • Elizabeth Fischer
  • Alicia Klinvex

Recent PRs of interest

Discussion (solicited)

  • Mike: installing a set of dependencies. Each of the packages has a configure script that specifies valid versions for dependencies

    • It would be nice to extract version ranges from configure scripts that are provided with packages
    • Patrick: also running into the same issue. For now this is worked-around somewhat by specifying exact versions in depends_on
    • In https://github.com/spack/spack/pull/7753 for example no versions are specified in depends_on directives, but the installation line does specify versions. Some of this was also resolved by specifying packages as externals.
    • Mike: are the gnome dependencies like LLVM, in that there are extra libraries that move up in versions in tandem with one another
      • Perhaps it makes sense to make a super package that aggregates a set of gnome deps together. Depending on a specific version of the super package in turn translates into a set of specific underlying package dependencies.

  • In progress PR to refactor initialization: https://github.com/spack/spack/pull/7774

    • Make Spack load faster (move out things that are loaded every time Spack is run but not used every time)
    • Provides a path towards user-specified configuration directories
    • Fairly large and likely to touch many other core PRs

  • Spack Setup capabilities being added to Spack Environments https://github.com/spack/spack/pull/7830 Here are some real Spack setup / environment command lines that work, but I don't like them...

    • bin/spack --debug install --fake --setup everytrace,hwloc everytrace
    • bin/spack --debug env add --setup everytrace c1 everytrace

  • Patrick: spack-not-using-already-installed-packages strikes again

    • Does specifying hashes of already-installed packages work in the meantime?
    • New concretizer + environments may help: concretizer tries to use already-installed instances of packages
Add a custom footer
Clone this wiki locally