Hi folks,

yet another small patch.

While building/installing openvas-server our buildkit detected that
openvas-libraries and openvas-server try to install 'includes.h' which
is bad practice for packaging.

For now I made a small patch for openvas-server introducing a simple
test if 'includes.h' is already in place, but maybe it is more wise to
decide which of both components will install it.

Cheers,
Christian

--- openvas-server-0.9.0/Makefile.orig	2007-09-18 02:16:13.000000000 +0200
+++ openvas-server-0.9.0/Makefile	2007-09-18 02:18:20.000000000 +0200
@@ -79,7 +79,7 @@
 	$(INSTALL) -m 755 openvas-rmuser ${sbindir}/openvas-rmuser
 	$(INSTALL) -m 755 openvas-mkcert ${sbindir}/openvas-mkcert
 	$(INSTALL) -c -m 0444 openvas-services ${localstatedir}/lib/openvas/openvas-services
-	$(INSTALL) -c -m 0444 include/includes.h ${includedir}/openvas/includes.h
+	@test -f ${includedir}/openvas/includes.h || $(INSTALL) -c -m 0444 include/includes.h ${includedir}/openvas/includes.h
 	$(INSTALL) -c -m 0444 include/openvas-devel.h ${includedir}/openvas/openvas-devel.h
 	$(INSTALL) -c -m 0444 include/config.h ${includedir}/openvas/config.h
 	$(INSTALL) -c -m 0444 include/threadcompat.h ${includedir}/openvas/threadcompat.h

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Openvas-devel mailing list
Openvas-devel@wald.intevation.org
http://lists.wald.intevation.org/mailman/listinfo/openvas-devel

Reply via email to