[pve-devel] [PATCH manager] use git rev-parse for repoid
Dominik Csapak
d.csapak at proxmox.com
Wed Jun 14 12:22:28 CEST 2017
instead of getting the repoid from .git/refs/heads/master
using HEAD as commit also means we get the correct commit hash for when
building the package (e.g. when building from stable-4)
Signed-off-by: Dominik Csapak <d.csapak at proxmox.com>
---
since changing the build to dpkg-buildpackage we would get an empty
string, because we do not copy the .git dir to dest
PVE/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/PVE/Makefile b/PVE/Makefile
index ac230fbf..33c110be 100644
--- a/PVE/Makefile
+++ b/PVE/Makefile
@@ -14,7 +14,7 @@ PERLSOURCE = \
all: pvecfg.pm ${SUBDIRS}
-REPOID=`../repoid.pl ../.git`
+REPOID=$(shell git rev-parse --short HEAD)
pvecfg.pm: pvecfg.pm.in
sed -e s/@VERSION@/${VERSION}/ -e s/@PACKAGERELEASE@/${PACKAGERELEASE}/ -e s/@PACKAGE@/${PACKAGE}/ -e s/@REPOID@/${REPOID}/ $< >$@.tmp
--
2.11.0
More information about the pve-devel
mailing list