Now that we are using git, I would like to propose that the maxima version
string contained in *autoconf-version* be more automatic and precise.
Currently, it's updated by hand (and has the value of 5.25post). With git
we can use 'git describe --dirty' to create a version for us that describes
the src version. (This doesn't quite work; more on that below.) My
current tree says "branch-5_25-base-212-g233544b-dirty". The "dirty" part
says I have local changes in the tree, branch-5_25-base was the last tag,
212 is the number of commits since then and 233544b is the git SHA1 hash of
that commit.
Implementing this is simple. We need autoconf to check that git is
available. If so, we can generate the appropriate version. If git is not
available, we can just use the (hand-maintained) 5.25post.
There is one issue mentioned above. Currently, we have to use "git
describe --tags --dirty" instead of "git describe --dirty" because there
are no annotated tags. We should probably create annotated tags when tag
the releases.
Ray
diff --git a/configure.in b/configure.in
index 9249641..7d14896 100644
--- a/configure.in
+++ b/configure.in
@@ -75,6 +75,13 @@ if test x"${clisp}" = xtrue ; then
fi
fi
+dnl Append a git version to the version, if we have git available.
+AC_CHECK_PROG(have_git, git, yes, no)
+
+case ${have_git} in
+ yes) VERSION=${VERSION}-`git describe --tags --dirty` ;;
+esac
+
dnl n.b. cmucl_default_name is hardcoded in "with" message
cmucl_default_name=lisp
CMUCL_RUNTIME=lisp