summaryrefslogtreecommitdiff
path: root/devel/libwnck
diff options
context:
space:
mode:
authordsainty <dsainty@pkgsrc.org>2010-03-31 03:50:25 +0000
committerdsainty <dsainty@pkgsrc.org>2010-03-31 03:50:25 +0000
commitd97ecae20e10a18fb916177bf1d018ee5c13350f (patch)
tree5c3dee68d5bb36a6f7457afb38b5edf61e363e0e /devel/libwnck
parent670e784a8f36dc9154b912103e3aae109546ae88 (diff)
downloadpkgsrc-d97ecae20e10a18fb916177bf1d018ee5c13350f.tar.gz
libwnck can use libXres if configure finds it, but it wasn't buildinked in.
If configure finds it in the base system anyway, bad things will happen (like the package build breaking, as experienced under Linux). So, buildlink in libXres. Bump PKGREVISION to reflect that this version was built with libXres definitely present.
Diffstat (limited to 'devel/libwnck')
-rw-r--r--devel/libwnck/Makefile4
1 files changed, 3 insertions, 1 deletions
diff --git a/devel/libwnck/Makefile b/devel/libwnck/Makefile
index 353d8ae9fc2..f4820cd6c92 100644
--- a/devel/libwnck/Makefile
+++ b/devel/libwnck/Makefile
@@ -1,7 +1,8 @@
-# $NetBSD: Makefile,v 1.67 2009/10/22 17:06:35 drochner Exp $
+# $NetBSD: Makefile,v 1.68 2010/03/31 03:50:25 dsainty Exp $
#
DISTNAME= libwnck-2.28.0
+PKGREVISION= 1
CATEGORIES= devel x11 gnome
MASTER_SITES= ${MASTER_SITE_GNOME:=sources/libwnck/2.28/}
EXTRACT_SUFX= .tar.bz2
@@ -25,6 +26,7 @@ PKGCONFIG_OVERRIDE= libwnck-1.0.pc.in
.include "../../x11/startup-notification/buildlink3.mk"
BUILDLINK_API_DEPENDS.gtk2+= gtk2+>=2.6.0
.include "../../x11/gtk2/buildlink3.mk"
+.include "../../x11/libXres/buildlink3.mk"
.include "../../x11/libSM/buildlink3.mk"
.include "../../x11/libX11/buildlink3.mk"
BUILDLINK_DEPMETHOD.libXt?= build