pkgsrc/x11/vte/buildlink3.mk

# $NetBSD: buildlink3.mk,v 1.14 2006/07/08 23:11:16 jlam Exp $

BUILDLINK_DEPTH:=	${BUILDLINK_DEPTH}+
VTE_BUILDLINK3_MK:=	${VTE_BUILDLINK3_MK}+

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

BUILDLINK_PACKAGES:=	${BUILDLINK_PACKAGES:Nvte}
BUILDLINK_PACKAGES+=	vte
BUILDLINK_ORDER:=	${BUILDLINK_ORDER} ${BUILDLINK_DEPTH}vte

.if !empty(VTE_BUILDLINK3_MK:M+)
BUILDLINK_API_DEPENDS.vte+=		vte>=0.11.11
BUILDLINK_ABI_DEPENDS.vte+=	vte>=0.12.0nb1
BUILDLINK_PKGSRCDIR.vte?=	../../x11/vte
.endif	# VTE_BUILDLINK3_MK

.include "../../devel/glib2/buildlink3.mk"
.include "../../devel/pango/buildlink3.mk"
.include "../../x11/gtk2/buildlink3.mk"
.include "../../x11/libzvt/buildlink3.mk"

BUILDLINK_DEPTH:=	${BUILDLINK_DEPTH:S/+$//}
Change the format of BUILDLINK_ORDER to contain depth information as well, and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto 2006-07-09 01:10:35 +02:00			`# $NetBSD: buildlink3.mk,v 1.14 2006/07/08 23:11:16 jlam Exp $`
bl3ify 2004-02-11 08:11:28 +01:00
			`BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH}+`
			`VTE_BUILDLINK3_MK:= ${VTE_BUILDLINK3_MK}+`

			`.if !empty(BUILDLINK_DEPTH:M+)`
			`BUILDLINK_DEPENDS+= vte`
			`.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:Nvte}`
			`BUILDLINK_PACKAGES+= vte`
Change the format of BUILDLINK_ORDER to contain depth information as well, and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto 2006-07-09 01:10:35 +02:00			`BUILDLINK_ORDER:= ${BUILDLINK_ORDER} ${BUILDLINK_DEPTH}vte`
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
bl3ify 2004-02-11 08:11:28 +01:00			`.if !empty(VTE_BUILDLINK3_MK:M+)`
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.vte+= vte>=0.11.11`
Bump BUILDLINK_ABI_DEPENDS.png and PKGREVISION for png-1.2.9nb2 update. 2006-04-17 15:45:57 +02:00			`BUILDLINK_ABI_DEPENDS.vte+= vte>=0.12.0nb1`
bl3ify 2004-02-11 08:11:28 +01:00			`BUILDLINK_PKGSRCDIR.vte?= ../../x11/vte`
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 # VTE_BUILDLINK3_MK`
bl3ify 2004-02-11 08:11:28 +01:00
Explicitly include buildlink3 files of packages directly used. 2004-11-06 17:52:57 +01:00			`.include "../../devel/glib2/buildlink3.mk"`
			`.include "../../devel/pango/buildlink3.mk"`
bl3ify 2004-02-11 08:11:28 +01:00			`.include "../../x11/gtk2/buildlink3.mk"`
			`.include "../../x11/libzvt/buildlink3.mk"`

Aligned the last line of the buildlink3.mk files with the first line, so that they look nicer. 2006-04-12 12:26:59 +02:00			`BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH:S/+$//}`