spack/lib/spack
Scott Wittenburg 56894b8805 Support yaml paths anywhere specs are handled on CLI (#12561)
Update command-line (CLI) parsing to understand references to yaml
files that store Spack specs. Where a file reference is encountered,
the full Spec in the file will be read in. A file reference may
appear anywhere that a spec could appear before. For example, if you
write "spack spec -y openmpi > openmpi.yaml" you may then install the
spec using the yaml file by running "spack install ./openmpi.yaml";
you can also refer to dependencies in this way (e.g.
"spack install foo^./openmpi.yaml").

There are two requirements for file references:

* A file path entered on the CLI must include a "/" even if the file
  exists in your current working directory. For example, if you
  create an openmpi.yaml file as above and run
  "spack install openmpi.yaml" from the same directory, it will
  report an error.
* A file path entered on the CLI must end with ".yaml"

This commit adds error messages to clearly inform the user of both
violations.
2019-09-17 19:45:37 -07:00
..
docs Implement an optional compiler bootstrapping phase 2019-09-13 22:57:15 -07:00
env Add implicit rpaths to compiler detection (#7153) 2019-08-24 06:21:45 -07:00
external copyright: update license headers for 2013-2019 copyright. 2019-01-01 00:44:28 -08:00
llnl implicit rpaths filtering (#12789) 2019-09-17 17:45:21 -05:00
spack Support yaml paths anywhere specs are handled on CLI (#12561) 2019-09-17 19:45:37 -07:00