pkgsrc/devel/ldapsdk/Makefile

# $NetBSD: Makefile,v 1.6 2001/10/26 14:10:00 agc Exp $

DISTNAME=       ldapsdk_12311998
PKGNAME=        ldapsdk-12311998
CATEGORIES=	devel databases
MASTER_SITES=   ftp://ftp.mozilla.org/pub/directory/c-sdk/ldap/

MAINTAINER=     packages@netbsd.org
HOMEPAGE=	http://www.mozilla.org/directory/
COMMENT=	LDAP C-SDK from the Mozilla project

CONFLICTS+=	openldap*

USE_GMAKE=	yes
USE_PERL5=	yes
WRKSRC=         ${WRKDIR}/mozilla

do-build:
	cd ${.CURDIR} && ${SETENV} ${SCRIPTS_ENV} ${SH} ${SCRIPTDIR}/pre-build

do-install:
	cd ${.CURDIR} && ${SETENV} ${SCRIPTS_ENV} ${SH} ${SCRIPTDIR}/pre-install

.include "../../mk/bsd.pkg.mk"
At present, if there is a pre-<target> or post-<target> script in the scripts/ directory, it will be run automatically as part of the build process, by bsd.pkg.mk. There are now exactly 5 packages in pkgsrc which use this facility, and yet, for every package build, the existence of a script is checked by bsd.pkg.mk once before the target is executed, and once afterwards. This incurs needless overhead. Move the separate pre- and post- script handling out of bsd.pkg.mk into the individual package Makefiles, where it's much more obvious what is happening, anyway. 2001-10-26 16:09:59 +02:00			`# $NetBSD: Makefile,v 1.6 2001/10/26 14:10:00 agc Exp $`
The Mozilla project C-SDK for LDAP. A LDAP V3 client library. 1999-05-18 23:22:26 +02:00
			`DISTNAME= ldapsdk_12311998`
			`PKGNAME= ldapsdk-12311998`
			`CATEGORIES= devel databases`
			`MASTER_SITES= ftp://ftp.mozilla.org/pub/directory/c-sdk/ldap/`

			`MAINTAINER= packages@netbsd.org`
			`HOMEPAGE= http://www.mozilla.org/directory/`
Lose leading '(The\|the) ' from COMMENT 2001-05-17 10:38:42 +02:00			`COMMENT= LDAP C-SDK from the Mozilla project`
The Mozilla project C-SDK for LDAP. A LDAP V3 client library. 1999-05-18 23:22:26 +02:00
			`CONFLICTS+= openldap*`

it seems this package wants perl to build 2000-01-11 22:01:05 +01:00			`USE_GMAKE= yes`
			`USE_PERL5= yes`
The Mozilla project C-SDK for LDAP. A LDAP V3 client library. 1999-05-18 23:22:26 +02:00			`WRKSRC= ${WRKDIR}/mozilla`

			`do-build:`
At present, if there is a pre-<target> or post-<target> script in the scripts/ directory, it will be run automatically as part of the build process, by bsd.pkg.mk. There are now exactly 5 packages in pkgsrc which use this facility, and yet, for every package build, the existence of a script is checked by bsd.pkg.mk once before the target is executed, and once afterwards. This incurs needless overhead. Move the separate pre- and post- script handling out of bsd.pkg.mk into the individual package Makefiles, where it's much more obvious what is happening, anyway. 2001-10-26 16:09:59 +02:00			`cd ${.CURDIR} && ${SETENV} ${SCRIPTS_ENV} ${SH} ${SCRIPTDIR}/pre-build`
The Mozilla project C-SDK for LDAP. A LDAP V3 client library. 1999-05-18 23:22:26 +02:00
			`do-install:`
At present, if there is a pre-<target> or post-<target> script in the scripts/ directory, it will be run automatically as part of the build process, by bsd.pkg.mk. There are now exactly 5 packages in pkgsrc which use this facility, and yet, for every package build, the existence of a script is checked by bsd.pkg.mk once before the target is executed, and once afterwards. This incurs needless overhead. Move the separate pre- and post- script handling out of bsd.pkg.mk into the individual package Makefiles, where it's much more obvious what is happening, anyway. 2001-10-26 16:09:59 +02:00			`cd ${.CURDIR} && ${SETENV} ${SCRIPTS_ENV} ${SH} ${SCRIPTDIR}/pre-install`
The Mozilla project C-SDK for LDAP. A LDAP V3 client library. 1999-05-18 23:22:26 +02:00
			`.include "../../mk/bsd.pkg.mk"`