sami7777/triangles_v5
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix version detection: prioritize exact tag match in genbuild.sh

Browse Source 
When building from a release tag (e.g. v5.4.1), git describe was finding
the nearest ancestor tag (v5.3.8) instead of the exact tag, resulting in
version strings like 'v5.3.8-9-gdfb4b22' instead of 'v5.4.1'.

Now genbuild.sh tries --exact-match first, falling back to distance-based
describe only when not on a tagged commit.
This commit is contained in:
Krystie
2026-03-27 23:02:04 -07:00
parent dfb4b221dd
commit a58eb3e9ef
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
share/genbuild.sh
Regular → Executable
+7 -2
View File
@@ -15,8 +15,13 @@ if [ -e "$(which git)" ]; then
# clean 'dirty' status of touched files that haven't been modified # clean 'dirty' status of touched files that haven't been modified
git diff >/dev/null 2>/dev/null git diff >/dev/null 2>/dev/null
# get a string like "v0.6.0-66-g59887e8-dirty" # Try exact tag match first (when building from a release tag)
DESC="$(git describe --dirty 2>/dev/null)" DESC="$(git describe --tags --exact-match 2>/dev/null)"
# If no exact match, fall back to git describe with commit distance
if [ -z "$DESC" ]; then
DESC="$(git describe --tags --dirty 2>/dev/null)"
fi
# get a string like "2012-04-10 16:27:19 +0200" # get a string like "2012-04-10 16:27:19 +0200"
TIME="$(git log -n 1 --format="%ci")" TIME="$(git log -n 1 --format="%ci")"