eedcbb0df1
The find-prefix infrastructure was required in a pkgviews world where packages installed from pkgsrc could have different installation prefixes, and this was a way for a dependency prefix to be determined. Now that pkgviews has been removed there is no longer any need for the overhead of this infrastructure. Instead we use BUILDLINK_PREFIX.pkg for dependencies pulled in via buildlink, or LOCALBASE/PREFIX where the dependency is coming from pkgsrc. Provides a reasonable performance win due to the reduction of `pkg_info -qp` calls, some of which were redundant anyway as they were duplicating the same information provided by BUILDLINK_PREFIX.pkg.
39 lines
1.1 KiB
Makefile
39 lines
1.1 KiB
Makefile
# $NetBSD: Makefile,v 1.35 2015/11/25 12:49:27 jperkin Exp $
|
|
|
|
PKGNAME= ${PYPKGPREFIX}-gdbm-${PY_DISTVERSION}
|
|
CATEGORIES= databases python
|
|
|
|
MAINTAINER= dolecek@ics.muni.cz
|
|
HOMEPAGE= http://www.python.org/doc/lib/module-gdbm.html
|
|
COMMENT= Python interface to gdbm - GNU database manager
|
|
|
|
USE_TOOLS+= patch
|
|
|
|
.include "../../lang/python/pyversion.mk"
|
|
.if !empty(PYPKGPREFIX:Mpy3?)
|
|
GDBM_MODNAME= _gdbm
|
|
.else
|
|
GDBM_MODNAME= gdbm
|
|
.endif
|
|
|
|
EXTRACT_ELEMENTS= ${PYSUBDIR}/Modules/${GDBM_MODNAME}module.c
|
|
PYDISTUTILSPKG= yes
|
|
PY_PATCHPLIST= yes
|
|
|
|
PY_SETUP_SUBST+= GDBMPREFIX=${BUILDLINK_PREFIX.gdbm}
|
|
PY_SETUP_SUBST+= GDBM_MODNAME=${GDBM_MODNAME}
|
|
PLIST_SUBST+= GDBM_MODNAME=${GDBM_MODNAME}
|
|
PYSETUPINSTALLARGS+= --install-lib ${PREFIX}/${PYLIB}/lib-dynload
|
|
|
|
# ignore errors due to missing files (EXTRACT_ELEMENTS!)
|
|
do-patch:
|
|
set -e; \
|
|
cd ${WRKSRC}; \
|
|
for f in ${PATCHDIR}/patch-*; do \
|
|
${PATCH} --batch < "$$f" || ${TRUE}; \
|
|
done
|
|
|
|
.include "../../databases/gdbm/buildlink3.mk"
|
|
.include "../../lang/python/extension.mk"
|
|
.include "../../lang/python/srcdist.mk"
|
|
.include "../../mk/bsd.pkg.mk"
|