|
@@ -60,10 +60,19 @@ MKIT_PROJ_PKGNAME=""
|
60
|
60
|
#
|
61
|
61
|
# Can be 'none' or 'btime'.
|
62
|
62
|
#
|
63
|
|
-# If 'btime', devel builds have also 'tXXXXXXXX' tag, where each
|
64
|
|
-# 'X' is a hexa-decimal digit of Unix timestamp taken when build
|
65
|
|
-# is initiated. This way, builds from same branch are guarranteed
|
66
|
|
-# to order based on build time (that is, until February 7th, 2106).
|
|
63
|
+# If 'btime', devel builds have also timestamp-based tag in format of
|
|
64
|
+# `t%Y%m%d%H%M%S`, that is, a small character 't' followed by timestamp
|
|
65
|
+# without non-digit characters. The timestamps are in UTC, ie. timezones
|
|
66
|
+# need not apply.
|
|
67
|
+#
|
|
68
|
+# This helps with deploying development builds where packaging system
|
|
69
|
+# is not SemVer-compliant and makes it hard to install arbitrary version.
|
|
70
|
+# For example, old yum version (as of RHEL-6) will not let you install
|
|
71
|
+# version that it deems older than is installed, making it hard to
|
|
72
|
+# continually upgrade during active development. While packaging
|
|
73
|
+# systems have their own rukes (and SemVer says both versions should be
|
|
74
|
+# considered same) this tag will make it more likely to "win" the build
|
|
75
|
+# you made later.
|
67
|
76
|
#
|
68
|
77
|
# Note that this makes devel and dirty builds non-deterministic,
|
69
|
78
|
# but does not affect clean builds (ie. builds from clean repo
|