3 ms·

> do prebuilt binaries rerouted to be installed in a predefined path they were built in or is it also flexible? Prebuilt binaries don't have to go in a fixed p

> do prebuilt binaries rerouted to be installed in a predefined path they were built in or is it also flexible? Prebuilt binaries don't have to go in a fixed prefix -- we'll relocate RPATHs, shebangs, strings in text files, and (as long as you build in a longer path than you install to -- see `padded_length` at https://spack.readthedocs.io/en/latest/config_yaml.html https://spack.readthedocs.io/en/latest/config_yaml.html) strings in binaries. There is not currently a way to see before you install if an install will be from binary or from source, but that is something we are working on.

eviks 4y ago
So how would I know whether the prebuilt binaries were built in a longer path than I install to? Is there at least a way to block source builds if the app is not in the binary cache to avoid any surprises (basically have manual override/confirmation instead of automatic fallbacks to source builds)?
- tgamblin 4y ago
  > So how would I know whether the prebuilt binaries were built in a longer path than I install to? All the public ones are built with very long padding; if you make your own you're currently on your own. > Is there at least a way to block source builds if the app is not in the binary cache to avoid any surprises (basically have manual override/confirmation instead of automatic fallbacks to source builds)? Yep: spack install --cache-only ...