Update MKit for test suites to v0.0.34

src/tdk/utils/mkit/include/facts.sh

@@ -54,6 +54,9 @@ git_fact() {
         latest_sha)
             git log -1 --pretty=format:%h HEAD
             ;;
+        latest_cdate)
+            git log -1 --format=%cd --date=unix HEAD
+            ;;
         *)
             warn "unknown git fact asked: $fact_name"
             ;;
@@ -140,12 +143,13 @@ semver() {
     local latest_tag    # latest git tag
     local commit        # commit indicator (CURRENT_BRANCH.gHASH)
     local dirty=F       # F if dirty, T if clean
-    local btime         # hex timestamp or nothing (see $MKIT_TTAG)
+    local btime         # timestamp or nothing (see $MKIT_TTAG)
     local suffix        # version suffix
     prerl=$(ini 1value project:prerl)
     case $MKIT_TTAG in
         none)   btime= ;;
-        btime)  btime=$(printf '%08x' "$(date +%s)") ;;
+        btime)  btime=$(date -u +%Y%m%d%H%M%S) ;;
+        ctime)  btime=$(date -d @"$(git_fact latest_cdate)" -u +%Y%m%d%H%M%S) ;;
     esac
     grep ":" <<<"$prerl" \
      && warn "colon in project:prerl may corrupt version data: $prerl"

src/tdk/utils/mkit/include/vars.sh

@@ -58,20 +58,32 @@ MKIT_PROJ_PKGNAME=""
 #
 # Add time-based ordinal tag to SemVer build data?
 #
-# Can be 'none' or 'btime'.
-#
-# If 'btime', devel builds have also 'tXXXXXXXX' tag, where each
-# 'X' is a hexa-decimal digit of Unix timestamp taken when build
-# is initiated.  This way, builds from same branch are guarranteed
-# to order based on build time (that is, until February 7th, 2106).
-#
-# Note that this makes devel and dirty builds non-deterministic,
-# but does not affect clean builds (ie. builds from clean repo
-# with HEAD corresponding to latest version tag.).
-#
-MKIT_TTAG=${MKIT_TTAG:-btime}
+# Can be 'none', 'ctime' or 'btime'.
+#
+# If 'ctime', devel builds have also timestamp-based tag in format of
+# `t%Y%m%d%H%M%S`, that is, a small character 't' followed by timestamp
+# without non-digit characters.  The timestamps are in UTC, ie. timezones
+# need not apply.  'btime' has the same format, except that it's derived
+# from build time, while 'ctime' is from last commit's commit date.
+#
+# This helps with deploying development builds where packaging system
+# is not SemVer-compliant and makes it hard to install arbitrary version.
+# For example, old yum version (as of RHEL-6) will not let you install
+# version that it deems older than is installed, making it hard to
+# continually upgrade during active development.  While packaging
+# systems have their own rukes (and SemVer says both versions should be
+# considered same) this tag will make it more likely to "win" the build
+# you made later.
+#
+# Note that this does not affect clean builds (ie. builds from clean
+# repo with HEAD corresponding to latest version tag.).
+#
+# Also note that 'btime' makes the version non-deterministic: merely
+# initiating the build a second later will result in different version.
+#
+MKIT_TTAG=${MKIT_TTAG:-ctime}
 
 #
 # This MKit version
 #
-MKIT_VERSION=0.0.33
+MKIT_VERSION=0.0.34