redict/src/mkreleasehdr.sh

#!/bin/sh
GIT_SHA1=`(git show-ref --head --hash=8 2> /dev/null || echo 00000000) | head -n1`
GIT_DIRTY=`git diff --no-ext-diff 2> /dev/null | wc -l`
BUILD_ID=`uname -n`"-"`date +%s`
if [ -n "$SOURCE_DATE_EPOCH" ]; then
  BUILD_ID=$(date -u -d "@$SOURCE_DATE_EPOCH" +%s 2>/dev/null || date -u -r "$SOURCE_DATE_EPOCH" +%s 2>/dev/null || date -u %s)
fi
test -f release.h || touch release.h
(cat release.h | grep SHA1 | grep $GIT_SHA1) && \
(cat release.h | grep DIRTY | grep $GIT_DIRTY) && exit 0 # Already up-to-date
echo "#define REDIS_GIT_SHA1 \"$GIT_SHA1\"" > release.h
echo "#define REDIS_GIT_DIRTY \"$GIT_DIRTY\"" >> release.h
echo "#define REDIS_BUILD_ID \"$BUILD_ID\"" >> release.h
touch release.c # Force recompile of release.c
buliding of release.h moved into an external script. Avoided recompialtion of redis.c if git sha1 is the same as the previous one 2010-05-17 18:36:48 -04:00			`#!/bin/sh`
fix compile error on solaris 2010-05-20 06:33:33 -04:00			GIT_SHA1=`(git show-ref --head --hash=8 2> /dev/null \|\| echo 00000000) \| head -n1`
suppress external diff program when using git diff. 2013-02-24 11:43:56 -05:00			GIT_DIRTY=`git diff --no-ext-diff 2> /dev/null \| wc -l`
Introduced the Build ID in INFO and --version output. The idea is to be able to identify a build in a unique way, so for instance after a bug report we can recognize that the build is the one of a popular Linux distribution and perform the debugging in the same environment. 2012-11-29 08:20:08 -05:00			BUILD_ID=`uname -n`"-"`date +%s`
Use SOURCE_DATE_EPOCH over unreproducible uname + date calls. See <https://reproducible-builds.org/specs/source-date-epoch/> for more details. Signed-off-by: Chris Lamb <chris@chris-lamb.co.uk> 2016-04-29 11:45:53 -04:00			`if [ -n "$SOURCE_DATE_EPOCH" ]; then`
			`BUILD_ID=$(date -u -d "@$SOURCE_DATE_EPOCH" +%s 2>/dev/null \|\| date -u -r "$SOURCE_DATE_EPOCH" +%s 2>/dev/null \|\| date -u %s)`
			`fi`
buliding of release.h moved into an external script. Avoided recompialtion of redis.c if git sha1 is the same as the previous one 2010-05-17 18:36:48 -04:00			`test -f release.h \|\| touch release.h`
			`(cat release.h \| grep SHA1 \| grep $GIT_SHA1) && \`
Fixed many typos. 2013-01-16 12:00:20 -05:00			`(cat release.h \| grep DIRTY \| grep $GIT_DIRTY) && exit 0 # Already up-to-date`
buliding of release.h moved into an external script. Avoided recompialtion of redis.c if git sha1 is the same as the previous one 2010-05-17 18:36:48 -04:00			`echo "#define REDIS_GIT_SHA1 \"$GIT_SHA1\"" > release.h`
build fixed when simpler shells are used to create release.h 2010-05-18 06:17:51 -04:00			`echo "#define REDIS_GIT_DIRTY \"$GIT_DIRTY\"" >> release.h`
Introduced the Build ID in INFO and --version output. The idea is to be able to identify a build in a unique way, so for instance after a bug report we can recognize that the build is the one of a popular Linux distribution and perform the debugging in the same environment. 2012-11-29 08:20:08 -05:00			`echo "#define REDIS_BUILD_ID \"$BUILD_ID\"" >> release.h`
Fixed deps in makefile and mkreleasehdr.sh script to really take advantage of the new trick to avoid recompilation of redis.c on git sha1 or dirty status change 2010-06-13 17:51:43 -04:00			`touch release.c # Force recompile of release.c`