[pve-devel] [PATCH cluster v2] buildsys: write control file into build directory

Thomas Lamprecht t.lamprecht at proxmox.com
Wed Feb 8 11:24:55 CET 2017


Else the first make {deb,dinstall} from a clean repo fails as we
generated the debian control file to the source debian/ folder.
Just write it directly to the build/debian directory, so we do not
clutter the source directory and build always with the up to date
control file.

Signed-off-by: Thomas Lamprecht <t.lamprecht at proxmox.com>
---

changes v1 -> v2:
* wirte the control file directly to the build directory instead of the
  source one, same effect as v1 but does not clutters source directory.

 Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index e5d61de..5adb5b3 100644
--- a/Makefile
+++ b/Makefile
@@ -26,7 +26,7 @@ ${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
+	sed -e "s|@PERLAPI@|perlapi-$(PERL_APIVER)|g" debian/control.in > build/debian/control
 	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





More information about the pve-devel mailing list