diff options
| author | reed <reed> | 2005-05-18 18:50:19 +0000 |
|---|---|---|
| committer | reed <reed> | 2005-05-18 18:50:19 +0000 |
| commit | 8e5348d095bd7010c4dfcc2176c948d1886820a6 (patch) | |
| tree | 0efe6a1bf51676bda55c4fecc5244af5ac6f3201 /sysutils | |
| parent | f02fc4f109f4d3df4ba55d97329d25525162e46b (diff) | |
| download | pkgsrc-8e5348d095bd7010c4dfcc2176c948d1886820a6.tar.gz | |
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 (limited to 'sysutils')
| -rw-r--r-- | sysutils/gnome-vfs2/buildlink3.mk | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/sysutils/gnome-vfs2/buildlink3.mk b/sysutils/gnome-vfs2/buildlink3.mk index aa7c56fe1cb..d4ce789d830 100644 --- a/sysutils/gnome-vfs2/buildlink3.mk +++ b/sysutils/gnome-vfs2/buildlink3.mk @@ -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 @@ BUILDLINK_PACKAGES+= gnome-vfs2 .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/ \ |