aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorMichael Nottebrock <lofi@FreeBSD.org>2005-07-11 10:37:26 +0000
committerMichael Nottebrock <lofi@FreeBSD.org>2005-07-11 10:37:26 +0000
commit2f6ec9e2696d5d25d8990f5f489c91adb651876e (patch)
treee00fd3e5fb9a07bdd4d426d9a04d6e114fd55250 /UPDATING
parent3cbd1264410cd2b6b7217339b09b5c6c3a4d5c47 (diff)
downloadports-2f6ec9e2696d5d25d8990f5f489c91adb651876e.tar.gz
ports-2f6ec9e2696d5d25d8990f5f489c91adb651876e.zip
Notes
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING15
1 files changed, 8 insertions, 7 deletions
diff --git a/UPDATING b/UPDATING
index 844d035a5b5a..31495b10877c 100644
--- a/UPDATING
+++ b/UPDATING
@@ -13,18 +13,19 @@ upgrades.
If you have compiled qt33 with the KDE_OPTIONS option checked (if your
installed qt-package is called qt-copy-3.3.4 instead of qt-3.3.4, check
- with pkg_info), you should cvsup and recompile both qt33, kdelibs3 and
- everything depending on it (in that order):
+ with pkg_info), you should cvsup and recompile qt33 and everything
+ depending on it:
- portupgrade -f qt\* && portupgrade -fr kdelibs\*
+ portupgrade -rf qt\*
Previous versions of the qt33 port contained a patch that
- introduces binary incompatibility between kdelibs and an unpatched qt33,
- if kdelibs has been compiled against a patched qt33.
+ introduces binary incompatibility between unpatched qt33 and software
+ compiled against a patched qt33.
Symptoms of the binary incompatibility: Unresolved symbol warnings from
- various KDE applications, "Could not start kdeinit" dialogs during KDE
- startup, kicker crashes during exiting KDE.
+ various KDE/Qt applications (both during runtime or compiling/linking),
+ "Could not start kdeinit" dialogs during KDE startup, kicker crashes during
+ exiting KDE.
20050630:
AFFECTS: users of x11/nvidia-driver