summaryrefslogtreecommitdiff
path: root/aclocal.m4
diff options
context:
space:
mode:
authorIan Lynagh <ian@well-typed.com>2013-06-07 22:37:04 +0100
committerIan Lynagh <ian@well-typed.com>2013-06-07 22:37:04 +0100
commit0d860381cdca9ed9d92dc315358072a84696ba08 (patch)
tree00cafb2cfec31fa3ecb1f5cf11fddb69fb0d1767 /aclocal.m4
parenta28731b3a14ff6ef9c7dca8327d073e6ebb6b773 (diff)
downloadhaskell-0d860381cdca9ed9d92dc315358072a84696ba08.tar.gz
Improve the version numbers generated by the build system
If we can't find a better date to use, then use today's date.
Diffstat (limited to 'aclocal.m4')
-rw-r--r--aclocal.m49
1 files changed, 9 insertions, 0 deletions
diff --git a/aclocal.m4 b/aclocal.m4
index 10c460bbfa..be0d113d36 100644
--- a/aclocal.m4
+++ b/aclocal.m4
@@ -1551,6 +1551,15 @@ if test "$RELEASE" = "NO"; then
AC_MSG_RESULT(given $PACKAGE_VERSION)
else
AC_MSG_WARN([cannot determine snapshot version: no .git directory and no VERSION file])
+ dnl We'd really rather this case didn't happenm but it might
+ dnl do (in particular, people using lndir trees may find that
+ dnl the build system can't find any other date). If it does
+ dnl happen, then we use the current date.
+ dnl This way we get some idea about how recent a build is.
+ dnl It also means that packages built for 2 different builds
+ dnl will probably use different version numbers, so things are
+ dnl less likely to go wrong.
+ PACKAGE_VERSION=${PACKAGE_VERSION}.`date +%Y%m%d`
fi
fi