pkgsrc/security/libassuan/buildlink3.mk

# $NetBSD: buildlink3.mk,v 1.11 2012/05/07 01:53:56 dholland Exp $

BUILDLINK_TREE+=	libassuan

.if !defined(LIBASSUAN_BUILDLINK3_MK)
LIBASSUAN_BUILDLINK3_MK:=

BUILDLINK_API_DEPENDS.libassuan+=	libassuan>=1.0.0
BUILDLINK_API_DEPENDS.libassuan+=	libassuan<2.0.0
BUILDLINK_ABI_DEPENDS.libassuan+=	libassuan>=1.0.5nb1
BUILDLINK_PKGSRCDIR.libassuan?=	../../security/libassuan

.include "../../security/libgpg-error/buildlink3.mk"
.endif # LIBASSUAN_BUILDLINK3_MK

BUILDLINK_TREE+=	-libassuan
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.11 2012/05/07 01:53:56 dholland Exp $`
IPC library used by gnupg-devel. 2004-10-23 15:27:36 +02: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+= libassuan`
IPC library used by gnupg-devel. 2004-10-23 15:27:36 +02: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(LIBASSUAN_BUILDLINK3_MK)`
			`LIBASSUAN_BUILDLINK3_MK:=`
IPC library used by gnupg-devel. 2004-10-23 15:27:36 +02:00
Update to 1.0.0. There are no actual code changes since the last release, only some cleanups and a complete manual. 2006-11-17 13:34:47 +01:00			`BUILDLINK_API_DEPENDS.libassuan+= libassuan>=1.0.0`
Do not accept libassuan>=2 here. 2010-07-17 14:07:10 +02:00			`BUILDLINK_API_DEPENDS.libassuan+= libassuan<2.0.0`
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.libassuan+= libassuan>=1.0.5nb1`
IPC library used by gnupg-devel. 2004-10-23 15:27:36 +02:00			`BUILDLINK_PKGSRCDIR.libassuan?= ../../security/libassuan`

			`.include "../../security/libgpg-error/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 # LIBASSUAN_BUILDLINK3_MK`
IPC library used by gnupg-devel. 2004-10-23 15:27:36 +02: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+= -libassuan`