Telcon: 2017 07 20
becker33 edited this page Jul 21, 2017
·
1 revision
- Ben Boeckel
- Greg Becker
- Patrick Gartung
- Paul Hopkins
- Flag handlers are here:
- default or per-flag
- see #4421
-
Build caches branch ready for merging?
- see #1013
- Record install path and all binary/text files
- put all that on a mirror somewhere
- Some trouble getting specs to match perfectly.
- use spec as concretized at build time, not current concretization
- use spec provenance from .spack/spec.yaml
- Does not work for external packages as of now
- Make all rpaths for things within spack tree use relative paths
- gpg signing
- can download keys from mirror and trust them
- code coverage (Patrick thinks some are coming from outside the diff)
-
Review
- Trying to speed up review process
-
octave Spack package
- includes link to compiler
- packages built against octave fail (outside of spack) on configure because octave points to spack wrapper.
- links should point through to the underlying compiler
- General issue with packages that include the compiler path in binary
- Python solves this with its filter_compilers method
- We could mimic this in other packages
- Paul Hopkins wonders whether this could be solved by creating a wrapper that includes all of the spack env variables necessary to run, so that they can be run externally without failing.