pkgsrc/sysutils/py-notify/buildlink3.mk

# $NetBSD: buildlink3.mk,v 1.10 2011/04/22 13:42:42 obache Exp $

BUILDLINK_TREE+=	py-notify

.if !defined(PY_NOTIFY_BUILDLINK3_MK)
PY_NOTIFY_BUILDLINK3_MK:=

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

BUILDLINK_API_DEPENDS.py-notify+=	${PYPKGPREFIX}-notify>=0.1.1
BUILDLINK_ABI_DEPENDS.py-notify?=	${PYPKGPREFIX}-notify>=0.1.1nb8
BUILDLINK_PKGSRCDIR.py-notify?=	../../sysutils/py-notify

.include "../../x11/py-gtk2/buildlink3.mk"
.endif # PY_NOTIFY_BUILDLINK3_MK

BUILDLINK_TREE+=	-py-notify
recursive bump from gettext-lib shlib bump. 2011-04-22 15:41:54 +02:00			`# $NetBSD: buildlink3.mk,v 1.10 2011/04/22 13:42:42 obache Exp $`
import py-notify-0.1.1 - Python bindings for libnotify 2007-01-10 11:40:52 +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-notify`
import py-notify-0.1.1 - Python bindings for libnotify 2007-01-10 11:40:52 +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_NOTIFY_BUILDLINK3_MK)`
			`PY_NOTIFY_BUILDLINK3_MK:=`
import py-notify-0.1.1 - Python bindings for libnotify 2007-01-10 11:40:52 +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"`

import py-notify-0.1.1 - Python bindings for libnotify 2007-01-10 11:40:52 +01:00			`BUILDLINK_API_DEPENDS.py-notify+= ${PYPKGPREFIX}-notify>=0.1.1`
recursive bump from gettext-lib shlib bump. 2011-04-22 15:41:54 +02:00			`BUILDLINK_ABI_DEPENDS.py-notify?= ${PYPKGPREFIX}-notify>=0.1.1nb8`
import py-notify-0.1.1 - Python bindings for libnotify 2007-01-10 11:40:52 +01:00			`BUILDLINK_PKGSRCDIR.py-notify?= ../../sysutils/py-notify`

			`.include "../../x11/py-gtk2/buildlink3.mk"`
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_NOTIFY_BUILDLINK3_MK`
import py-notify-0.1.1 - Python bindings for libnotify 2007-01-10 11:40:52 +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-notify`