[pkgsrc/trunk]: pkgsrc/sysutils/gnome-vfs2 Bump BUILDLINK_RECOMMENDED.gnome-v...

[reed <reed%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/def1d43353bd
branches:  trunk
changeset: 494046:def1d43353bd
user:      reed <reed%pkgsrc.org@localhost>
date:      Wed May 18 18:50:19 2005 +0000

description:
Bump BUILDLINK_RECOMMENDED.gnome-vfs2 to gnome-vfs2>=2.10.1.  Its
dependency gnutls had an SONAME change, so 2.10.0 could have been
built before and after this and so could have two diffferent packages
with same package name. This happened a couple weeks ago.  The
update for gnome-vfs2 2.10.1 happened after this.

(I never checked other software that may use libgnutls.)

diffstat:

 sysutils/gnome-vfs2/buildlink3.mk |  4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diffs (18 lines):

diff -r 9fcd459a18e9 -r def1d43353bd sysutils/gnome-vfs2/buildlink3.mk
--- a/sysutils/gnome-vfs2/buildlink3.mk Wed May 18 18:48:37 2005 +0000
+++ b/sysutils/gnome-vfs2/buildlink3.mk Wed May 18 18:50:19 2005 +0000
@@ -1,4 +1,4 @@
-# $NetBSD: buildlink3.mk,v 1.14 2005/04/15 01:59:29 rh Exp $
+# $NetBSD: buildlink3.mk,v 1.15 2005/05/18 18:50:19 reed Exp $
 
 BUILDLINK_DEPTH:=              ${BUILDLINK_DEPTH}+
 GNOME_VFS2_BUILDLINK3_MK:=     ${GNOME_VFS2_BUILDLINK3_MK}+
@@ -12,7 +12,7 @@
 
 .if !empty(GNOME_VFS2_BUILDLINK3_MK:M+)
 BUILDLINK_DEPENDS.gnome-vfs2+=         gnome-vfs2>=2.8.0
-BUILDLINK_RECOMMENDED.gnome-vfs2+=     gnome-vfs2>=2.10.0
+BUILDLINK_RECOMMENDED.gnome-vfs2+=     gnome-vfs2>=2.10.1
 BUILDLINK_PKGSRCDIR.gnome-vfs2?=       ../../sysutils/gnome-vfs2
 
 PRINT_PLIST_AWK+=      /^@dirrm lib\/gnome-vfs-2.0\/modules/ \