Telcon: 2022 11 30
Tamara Dahlgren edited this page Nov 30, 2022
·
15 revisions
Held Wednesday Nov. 30th, 9am PT
- Peter Scheibel (host)
- Mark Krentel
- David Doscher
- Davide DelVento
- Greg Becker
- Ivan Razumov
- Jonathon Anderson
- Massimiliano Culpo
- Richarda Butler
- Srinath Vadlamani
- Todd Gamblin
- Umashankar Sivakumar
- Bill Conn
- Phil Sakievich
- Tammy Dahlgren
- Brian van Essen
- The meaning of
buildable: false
- Should this allow using already-installed packages
- or... should it force only using an external
- Ivan: prefer
buildable: false
to only use externals (no Spack packages, even those previously installed by Spack) - Peter: how does this combine with manifest files: you consume the manifest and want to build with that
- These packages are already marked as having an external path (and are therefore external) so it could be that the concretizer simply needs to recognize specs added from the manifest as external
- Max: what if someone made a buildcache and you want to make sure you only use that for some packages?
- Todd: it would be good to have a "don't build" preference:
- Allow externals, already-installed things, and binary cache installs
- Todd: how do you say to use a specific external right now (in particular if you have more than one)
- Todd: it would be good to remove "buildable" and replace it with a number of designations for behavior
from: [source, external, buildcache, installed]
- Greg: the order should be installed, external, buildcache, source
- Peter: why is there an order
- (it was decided that there would be no order)
- (Mark) How to treat projects like binutils uses
make info
- Some filesystems disrupt the timestamps so
texinfo
is called (and for some packages isn't listed as a dependency) - Should we alter the timestamps so that the info files no-longer appear out of date
- Some filesystems disrupt the timestamps so