aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorChristian Weisgerber <naddy@FreeBSD.org>2012-07-21 13:52:14 +0000
committerChristian Weisgerber <naddy@FreeBSD.org>2012-07-21 13:52:14 +0000
commit1dd4460cb7a84ac62d8b302f54fe6a44baf0f095 (patch)
treef0eafa1da1464b22cc7287ea3dc3706931e82c7d /UPDATING
parent2a1bf99b32297d836310476934d08864d106c622 (diff)
downloadports-1dd4460cb7a84ac62d8b302f54fe6a44baf0f095.tar.gz
ports-1dd4460cb7a84ac62d8b302f54fe6a44baf0f095.zip
After the libogg 1.3.0 (ogg.8) update, recommend recursive rebuilding
of all dependent ports. It's the only way to reliably catch all indirect dependencies.
Notes
Notes: svn path=/head/; revision=301275
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING15
1 files changed, 15 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index a3eb4150efce..29e8b77f8a38 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,21 @@ they are unavoidable.
You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
+20120721
+ AFFECTS: users of audio/libogg
+ AUTHOR: naddy@FreeBSD.org
+
+ There is a new version of libogg (1.3.0) and the shared library version
+ has been bumped (ogg.7 to ogg.8). All ports that have an identifiable
+ direct dependency on this library have had their PORTREVISIONs bumped.
+ However, some ports that pull in the library indirectly may continue to
+ look for the old version. To ensure that all are updated, perform this
+ step:
+
+ # portmaster -r libogg
+ or
+ # portupgrade -rf libogg
+
20120717:
AFFECTS: users of ftp/proftpd
AUTHOR: mm@FreeBSD.org