| Age | Commit message (Collapse) | Author |
|---|
|
`git describe` produces "v1.3.1-2-gfbb7", which is neither a Semantic
Version nor especially readable. Derive the version from the most recent
release tag and the number of commits made since it instead, giving
"v1.3.1+7", and plain "v1.3.1" when building the tag itself.
That is a valid Semantic Version 2.0.0 with the commit distance as build
metadata. Note that build metadata is excluded from precedence, so
"v1.3.1+7" and "v1.3.1" compare equal; the distance identifies a build
rather than ordering it.
Tarball builds keep falling back to the version in the Makefile, and
release tags are expected to be named vMAJOR.MINOR.PATCH for the result
to stay well-formed.
Signed-off-by: Saya Andy <saya.andy@posteo.com>
|
|
Some people may clone the cgit repository and compile within a sandbox
or on another machine where git is not necessarily installed. When it
happens, cgit is getting compiled with an empty version number.
This commit fixes this.
|
|
Replacing '-' with '.' makes the version name slightly confusing, so lets
stick with the unmodified output of git describe.
Signed-off-by: Lars Hjemli <hjemli@gmail.com>
|
|
The old files were simply broken, hopefully the new ones will work out
somewhat better.
Signed-off-by: Lars Hjemli <hjemli@gmail.com>
|
|
A new script, gen-version.sh, is now invoked from 'make version' to generate
the file VERSION. This file contains a version identifier generated by
git-describe and is included in the Makefile.
Signed-off-by: Lars Hjemli <hjemli@gmail.com>
|
Saya Andy
Fabien C
Lars Hjemli
