spack/lib/spack
Todd Gamblin c029c8ff89 spack -V is now more descriptive for dev branches
`spack -V` previously always returned the version of spack from
`spack.spack_version`.  This gives us a general idea of what version
users are on, but if they're on `develop` or on some branch, we have to
ask more questions.

This PR makes `spack -V` check whether this instance of Spack is a git
repository, and if it is, it appends useful information from `git
describe --tags` to the version.  Specifically, it adds:

  - number of commits since the last release tag
  - abbreviated (but unique) commit hash

So, if you're on `develop` you might get something like this:

    $ spack -V
    0.13.3-912-3519a1762

This means you're on commit 3519a1762, which is 912 commits ahead of
the 0.13.3 release.

If you are on a release branch, or if you are using a tarball of Spack,
you'll get the usual `spack.spack_version`:

    $ spack -V
    0.13.3

This should help when asking users what version they are on, since a lot
of people use the `develop` branch.
2020-01-31 20:59:21 +01:00
..
docs Document how to use Spack to replace Homebrew/Conda (#13083) 2020-01-31 19:31:14 +01:00
env copyright: update copyright dates for 2020 (#14328) 2019-12-30 22:36:56 -08:00
external copyright: update copyright dates for 2020 (#14328) 2019-12-30 22:36:56 -08:00
llnl Fix handling of filter_file exceptions (#14651) 2020-01-28 12:49:26 -08:00
spack spack -V is now more descriptive for dev branches 2020-01-31 20:59:21 +01:00