pyenv/libexec/pyenv---version

#!/usr/bin/env bash
# Summary: Display the version of pyenv
#
# Displays the version number of this pyenv release, including the
# current revision from git, if available.
#
# The format of the git revision is:
#   <version>-<num_commits>-<git_sha>
# where `num_commits` is the number of commits since `version` was
# tagged.

set -e
[ -n "$PYENV_DEBUG" ] && set -x

version="1.2.1"
git_revision=""

if cd "${BASH_SOURCE%/*}" 2>/dev/null && git remote -v 2>/dev/null | grep -q pyenv; then
  git_revision="$(git describe --tags HEAD 2>/dev/null || true)"
  git_revision="${git_revision#v}"
fi

echo "pyenv ${git_revision:-$version}"
import `pyenv---version` from rbenv 2013-01-17 14:17:41 +00:00			`#!/usr/bin/env bash`
			`# Summary: Display the version of pyenv`
			`#`
			`# Displays the version number of this pyenv release, including the`
			`# current revision from git, if available.`
			`#`
			`# The format of the git revision is:`
			`# <version>-<num_commits>-<git_sha>`
			# where `num_commits` is the number of commits since `version` was
			`# tagged.`

			`set -e`
			`[ -n "$PYENV_DEBUG" ] && set -x`

Update changelog for 1.2.1 release 2018-01-10 13:27:34 +00:00			`version="1.2.1"`
Improve `rbenv --version` git checkout discovery When `rbenv --version` is called, this now happens: 1. It changes into the directory where `libexec/rbenv--version` resides and checks if it's a checkout of the rbenv repo (as opposed to Homebrew checkout or something else). Then it reads the git revision. 2. If that failed, change to `$RBENV_ROOT` directory and repeat step 1. 2015-10-25 15:54:38 +00:00			`git_revision=""`
import `pyenv---version` from rbenv 2013-01-17 14:17:41 +00:00
Merge remote-tracking branch 'rbenv/master' into rbenv-1.0 2016-03-02 01:39:52 +00:00			`if cd "${BASH_SOURCE%/*}" 2>/dev/null && git remote -v 2>/dev/null \| grep -q pyenv; then`
Improve `git --version` git revision lookup It doesn't try to chdir into RBENV_ROOT anymore because that might be a location of an unrelated rbenv install that might have a different version than the current one that is installed e.g. via a package manager such as Homebrew. Now just tries the repo where the source files (`libexec/*`) are located, and if that isn't a valid rbenv repo, bail out early. 2015-12-24 02:52:33 +00:00			`git_revision="$(git describe --tags HEAD 2>/dev/null \|\| true)"`
			`git_revision="${git_revision#v}"`
			`fi`
import `pyenv---version` from rbenv 2013-01-17 14:17:41 +00:00
			`echo "pyenv ${git_revision:-$version}"`