diff options
author | Todd Gamblin <gamblin2@llnl.gov> | 2022-02-21 11:46:37 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-02-21 11:46:37 -0800 |
commit | 7912a8e90b296ad648f2d86651931746fc1826f6 (patch) | |
tree | c543356b0e4ac72f54c0049658426ad4b5f4747a /bin | |
parent | 2210f84a91e56ecbfc4c41c0c5e5a84c8d2569d9 (diff) | |
download | spack-7912a8e90b296ad648f2d86651931746fc1826f6.tar.gz spack-7912a8e90b296ad648f2d86651931746fc1826f6.tar.bz2 spack-7912a8e90b296ad648f2d86651931746fc1826f6.tar.xz spack-7912a8e90b296ad648f2d86651931746fc1826f6.zip |
bugfix: Not all concrete versions on the CLI should be considered real (#28620)
Some "concrete" versions on the command line, e.g. `qt@5` are really
meant to satisfy some actual concrete version from a package. We should
only assume the user is introducing a new, unknown version on the CLI
if we, well, don't know of any version that satisfies the user's
request. So, if we know about `5.11.1` and `5.11.3` and they ask for
`5.11.2`, we'd ask the solver to consider `5.11.2` as a solution. If
they just ask for `5`, though, `5.11.1` or `5.11.3` are fine solutions,
as they satisfy `@5`, so use them.
Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>
Diffstat (limited to 'bin')
0 files changed, 0 insertions, 0 deletions