summaryrefslogtreecommitdiff
path: root/.readthedocs.yml
diff options
context:
space:
mode:
authorPeter Scheibel <scheibel1@llnl.gov>2021-02-23 11:45:50 -0800
committerTodd Gamblin <tgamblin@llnl.gov>2021-05-22 11:51:20 -0700
commit5546b22c70585c956ad9fd88f68d8139ff966ded (patch)
tree1428cb835a7d7f73b1b62fabbbf51ea92e29dbc6 /.readthedocs.yml
parent2496c7b514a500da032218960cf8b8e50cc7d29d (diff)
downloadspack-5546b22c70585c956ad9fd88f68d8139ff966ded.tar.gz
spack-5546b22c70585c956ad9fd88f68d8139ff966ded.tar.bz2
spack-5546b22c70585c956ad9fd88f68d8139ff966ded.tar.xz
spack-5546b22c70585c956ad9fd88f68d8139ff966ded.zip
"spack build-env" searches env for relevant spec (#21642)
If you install packages using spack install in an environment with complex spec constraints, and the install fails, you may want to test out the build using spack build-env; one issue (particularly if you use concretize: together) is that it may be hard to pass the appropriate spec that matches what the environment is attempting to install. This updates the build-env command to default to pulling a matching spec from the environment rather than concretizing what the user provides on the command line independently. This makes a similar change to spack cd. If the user-provided spec matches multiple specs in the environment, then these commands will now report an error and display all matching specs (to help the user specify). Co-authored-by: Gregory Becker <becker33@llnl.gov>
Diffstat (limited to '.readthedocs.yml')
0 files changed, 0 insertions, 0 deletions