pkgsrc/time/py-mxDateTime/buildlink3.mk

# $NetBSD: buildlink3.mk,v 1.15 2012/05/07 01:54:04 dholland Exp $

BUILDLINK_TREE+=	py-mxDateTime

.if !defined(PY_MXDATETIME_BUILDLINK3_MK)
PY_MXDATETIME_BUILDLINK3_MK:=

.include "../../lang/python/pyversion.mk"

BUILDLINK_API_DEPENDS.py-mxDateTime+=	${PYPKGPREFIX}-mxDateTime>=2.0.5
BUILDLINK_ABI_DEPENDS.py-mxDateTime+=	${PYPKGPREFIX}-mxDateTime>=2.0.6nb1
BUILDLINK_PKGSRCDIR.py-mxDateTime?=	../../time/py-mxDateTime
BUILDLINK_INCDIRS.py-mxDateTime+=	${PYSITELIB}/mx/DateTime/mxDateTime
.endif # PY_MXDATETIME_BUILDLINK3_MK

BUILDLINK_TREE+=	-py-mxDateTime
Set BUILDLINK_ABI_DEPENDS correctly (with +=, not ?=) It turns out there were a lot of these. 2012-05-07 03:53:12 +02:00			`# $NetBSD: buildlink3.mk,v 1.15 2012/05/07 01:54:04 dholland Exp $`
bl3ify Patch provided by Michal Pasternak in PR 24664 (with fixes by me). 2004-03-04 12:11:30 +01:00
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time. 2009-03-20 20:23:50 +01:00			`BUILDLINK_TREE+= py-mxDateTime`
bl3ify Patch provided by Michal Pasternak in PR 24664 (with fixes by me). 2004-03-04 12:11:30 +01:00
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time. 2009-03-20 20:23:50 +01:00			`.if !defined(PY_MXDATETIME_BUILDLINK3_MK)`
			`PY_MXDATETIME_BUILDLINK3_MK:=`
bl3ify Patch provided by Michal Pasternak in PR 24664 (with fixes by me). 2004-03-04 12:11:30 +01:00
Include pyversion.mk include the protected part of the buildlink3.mk files, not over and over again. 2009-03-20 18:30:09 +01:00			`.include "../../lang/python/pyversion.mk"`

Over 1200 files touched but no revisions bumped :) RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day). 2006-04-06 08:21:32 +02:00			`BUILDLINK_API_DEPENDS.py-mxDateTime+= ${PYPKGPREFIX}-mxDateTime>=2.0.5`
Set BUILDLINK_ABI_DEPENDS correctly (with +=, not ?=) It turns out there were a lot of these. 2012-05-07 03:53:12 +02:00			`BUILDLINK_ABI_DEPENDS.py-mxDateTime+= ${PYPKGPREFIX}-mxDateTime>=2.0.6nb1`
Conform to template in revision 1.101 of bsd.buildlink3.mk. 2004-03-07 00:46:06 +01:00			`BUILDLINK_PKGSRCDIR.py-mxDateTime?= ../../time/py-mxDateTime`
D'oh! Fix typo: Only add the dir not the actual header.. 2004-03-04 16:02:59 +01:00			`BUILDLINK_INCDIRS.py-mxDateTime+= ${PYSITELIB}/mx/DateTime/mxDateTime`
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time. 2009-03-20 20:23:50 +01:00			`.endif # PY_MXDATETIME_BUILDLINK3_MK`
bl3ify Patch provided by Michal Pasternak in PR 24664 (with fixes by me). 2004-03-04 12:11:30 +01:00
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time. 2009-03-20 20:23:50 +01:00			`BUILDLINK_TREE+= -py-mxDateTime`