pkgsrc/security/libcrack/buildlink3.mk

# $NetBSD: buildlink3.mk,v 1.11 2009/03/20 19:25:18 joerg Exp $

BUILDLINK_TREE+=	libcrack

.if !defined(LIBCRACK_BUILDLINK3_MK)
LIBCRACK_BUILDLINK3_MK:=

BUILDLINK_API_DEPENDS.libcrack+=	libcrack>=2.7
BUILDLINK_ABI_DEPENDS.libcrack+=	libcrack>=2.7nb1
BUILDLINK_PKGSRCDIR.libcrack?=	../../security/libcrack
.endif # LIBCRACK_BUILDLINK3_MK

BUILDLINK_TREE+=	-libcrack
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			`# $NetBSD: buildlink3.mk,v 1.11 2009/03/20 19:25:18 joerg Exp $`
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework. 2004-01-04 00:06:43 +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+= libcrack`
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework. 2004-01-04 00:06:43 +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(LIBCRACK_BUILDLINK3_MK)`
			`LIBCRACK_BUILDLINK3_MK:=`
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework. 2004-01-04 00:06:43 +01:00
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.libcrack+= libcrack>=2.7`
			`BUILDLINK_ABI_DEPENDS.libcrack+= libcrack>=2.7nb1`
Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk. 2004-01-05 00:34:04 +01:00			`BUILDLINK_PKGSRCDIR.libcrack?= ../../security/libcrack`
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 # LIBCRACK_BUILDLINK3_MK`
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework. 2004-01-04 00:06:43 +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+= -libcrack`