pkgsrc/lang/pnet/buildlink3.mk

# $NetBSD: buildlink3.mk,v 1.4 2004/03/18 09:12:13 jlam Exp $

BUILDLINK_DEPTH:=	${BUILDLINK_DEPTH}+
PNET_BUILDLINK3_MK:=	${PNET_BUILDLINK3_MK}+

.if !empty(BUILDLINK_DEPTH:M+)
BUILDLINK_DEPENDS+=	pnet
.endif

BUILDLINK_PACKAGES:=	${BUILDLINK_PACKAGES:Npnet}
BUILDLINK_PACKAGES+=	pnet

.if !empty(PNET_BUILDLINK3_MK:M+)
BUILDLINK_DEPENDS.pnet+=	pnet>=0.6.2
BUILDLINK_PKGSRCDIR.pnet?=	../../lang/pnet
.endif	# PNET_BUILDLINK3_MK

.include "../../devel/zlib/buildlink3.mk"

BUILDLINK_DEPTH:=     ${BUILDLINK_DEPTH:S/+$//}
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES. 2004-03-18 10:12:08 +01:00			`# $NetBSD: buildlink3.mk,v 1.4 2004/03/18 09:12:13 jlam Exp $`
bl3ify 2004-02-27 08:37:04 +01:00
			`BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH}+`
			`PNET_BUILDLINK3_MK:= ${PNET_BUILDLINK3_MK}+`

			`.if !empty(BUILDLINK_DEPTH:M+)`
			`BUILDLINK_DEPENDS+= pnet`
			`.endif`

Reorder location and setting of BUILDLINK_PACKAGES to match template buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk. 2004-03-05 20:25:06 +01:00			`BUILDLINK_PACKAGES:= ${BUILDLINK_PACKAGES:Npnet}`
			`BUILDLINK_PACKAGES+= pnet`
bl3ify 2004-02-27 08:37:04 +01:00
Reorder location and setting of BUILDLINK_PACKAGES to match template buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk. 2004-03-05 20:25:06 +01:00			`.if !empty(PNET_BUILDLINK3_MK:M+)`
			`BUILDLINK_DEPENDS.pnet+= pnet>=0.6.2`
			`BUILDLINK_PKGSRCDIR.pnet?= ../../lang/pnet`
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES. 2004-03-18 10:12:08 +01:00			`.endif # PNET_BUILDLINK3_MK`
The pnet package uses zlib. 2004-03-11 09:06:56 +01:00
			`.include "../../devel/zlib/buildlink3.mk"`

bl3ify 2004-02-27 08:37:04 +01:00			`BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH:S/+$//}`