Skip to content
scheibelp edited this page Mar 22, 2018 · 15 revisions

Attendees

  • Patrick Gartung
  • Mario Melara
  • Levi Baber
  • Dave Montoya
  • Daniel Topa

Discussion Topics (solicited)

  • Resurgence of static vs. shared variants debate

    • May affect many packages, but we are not necessarily merging this soon
    • We are looking for a canonical way to indicate whether to build a shared libraries, static libraries, or both
    • There is also possibly a matter of concern whether to link against static libraries or shared libraries, although we felt that when building static libraries we may as well require that link dependencies are static (and likewise when building shared libraries require that all dependencies are built shared)
    • Previous discussion at: https://github.com/spack/spack/issues/5269
  • Patrick: nix includes dependency path in the hash of a package. Does Spack plan to do that?

    • No
    • Portage: just rebuilds the direct parents when a dependency is rebuilt (not sure how this works)
  • Are external packages included in the dag hash?

    • Spack constructs an abstract spec and hashes that (note that dependencies are stripped) - if the package is updated this doesn't change the spec dag hash
  • Build time tests: can you test a package after it is built

  • Daniel Topa: trilinos on power9

News

Clone this wiki locally