Else the first
$ make {deb,dinstall}
from a clean repo fails, as we generated the debian control file
after copying the debian folder to the build directory. The second
call to make worked as then the control was already generated, but it
could result in using an outdated control file.
Signed-off-by: Thomas Lamprecht <t.lampre...@proxmox.com>
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index e5d61de..a1686e4 100644
--- a/Makefile
+++ b/Makefile
@@ -25,8 +25,8 @@ ${DEB}:
rm -f *.deb
rm -rf build
cp -a data build
- cp -a debian build/debian
sed -e "s|@PERLAPI@|perlapi-$(PERL_APIVER)|g" debian/control.in >
debian/control
+ cp -a debian build/debian
echo "git clone git://git.proxmox.com/git/pve-cluster.git\\ngit
checkout ${GITVERSION}" > build/debian/SOURCE
cd build; ./autogen.sh
cd build; dpkg-buildpackage -rfakeroot -b -us -uc
--
2.1.4
_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
