Telcon: 2018 06 21
Michael Sternberg edited this page Jun 21, 2018
·
16 revisions
- Peter Scheibel (host)
- Mike Pozulp
- Michael Sternberg
- Greg Becker
- Alicia Klinvex
- Improved version detection using package URLs: https://github.com/spack/spack/pull/8429
- Michael: environment module packages and the module command
- Open PRs: 6451, 7536
- https://github.com/spack/spack/pull/6451#issuecomment-377079596
- https://github.com/spack/spack/pull/6451#issuecomment-377355714
- (Use the API that the shell gives) vs. (replicating module logic in spack)
- https://github.com/spack/spack/pull/7536
- Using python extensions installed in separate prefixes: https://github.com/spack/spack/pull/8436
- Supporting packages without compilers
-
https://github.com/spack/spack/issues/7550
- Related: don't propagate compilers from dependents always?
- Peter: could avoid propagating compilers across run-only dependencies
- https://github.com/spack/spack/issues/8531
- Greg: in the long run compilers will not be a field on Specs, but rather be treated like another dependency (and packages won't need to depend on a compiler package)
- Compilers are a build dependency that imposes a run dependency (e.g. the runtime libs for the package)
- One example is that many python extensions don't need a compiler
- Derivative issue: reinstallation of the intel-parallel-studio package (~10GB)
- Peter: I think setting Spack-installed packages as externals would help: https://github.com/spack/spack/pull/7759
-
https://github.com/spack/spack/issues/7550