diff options
| author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2022-08-31 22:05:55 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-08-31 20:05:55 +0000 |
| commit | 0c6e3188ac7ca780783bb36c0763c069cc0c1043 (patch) | |
| tree | 22ccc1c335bcbeb4cf8ab015e3d2d2001039eab8 /.dockerignore | |
| parent | 08261af4ab00ac124b9680fbc9b2b277727b0299 (diff) | |
| download | spack-0c6e3188ac7ca780783bb36c0763c069cc0c1043.tar.gz spack-0c6e3188ac7ca780783bb36c0763c069cc0c1043.tar.bz2 spack-0c6e3188ac7ca780783bb36c0763c069cc0c1043.tar.xz spack-0c6e3188ac7ca780783bb36c0763c069cc0c1043.zip | |
ASP-based solver: allow to reuse installed externals (#31558)
fixes #31484
Before this change if anything was matching an external
condition, it was considered "external" and thus something
to be "built".
This was happening in particular to external packages
that were re-read from the DB, which then couldn't be
reused, causing the problems shown in #31484.
This PR fixes the issue by excluding specs with a
"hash" from being considered "external"
* Test that users have a way to select a virtual
This ought to be solved by extending the "require"
attribute to virtual packages, so that one can:
```yaml
mpi:
require: 'multi-provider-mpi'
```
* Prevent conflicts to be enforced on specs that can be reused.
* Rename the "external_only" fact to "buildable_false", to better reflect its origin
Diffstat (limited to '.dockerignore')
0 files changed, 0 insertions, 0 deletions