diff options
author | Harmen Stoppels <me@harmenstoppels.nl> | 2024-05-29 08:25:34 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-05-29 08:25:34 +0200 |
commit | 70412612c79af495fb2b2223edac4bd5a70a813a (patch) | |
tree | ada06069c44fdf26dbdf839f5c525f919abf66f3 /LICENSE-MIT | |
parent | cd741c368ca3f0df4297d46092107a49e7698828 (diff) | |
download | spack-70412612c79af495fb2b2223edac4bd5a70a813a.tar.gz spack-70412612c79af495fb2b2223edac4bd5a70a813a.tar.bz2 spack-70412612c79af495fb2b2223edac4bd5a70a813a.tar.xz spack-70412612c79af495fb2b2223edac4bd5a70a813a.zip |
installer: improve init signature and explicits (#44374)
Change the installer to take `([pkg], args)` in the constructor instead
of `[(pkg, args)]`. The reason is that certain arguments are global
settings, and the new API ensures that those arguments cannot be
different across different "build requests".
The `explicit` install arg is now a list of hashes, and the installer is
no longer responsible for determining what package is installed
explicitly. This way environment installs can simply pass the list of
environment roots, without them necessarily being explicit build
requests. For example an env with two roots [a, b], where b depends on
a, would not always cause spack install to mark b as explicit.
Notice that `overwrite` already took a list of hashes, this makes
`explicit` consistent.
`package.do_install(explicit=True)` continues to take a boolean.
Diffstat (limited to 'LICENSE-MIT')
0 files changed, 0 insertions, 0 deletions