All, I've got SuSE 10 (from the commercial DVD) with KDE 3.4.2b. I wanted to try KDE 3.5. I've seen that people have tried it and experienced a few little problems - the kinds that I can live with. But nobody (unless I missed some mail) reported being thrown into dependency hell while installing the upgraded KDE. So, last night I downloaded everything from: http://mirror.cc.columbia.edu/pub/software/kde/stable/3.5/SuSE/ix86/10.0/ and tried to install/upgrade with YaST and then (when it got a little complicated for YaST) with rpm from the command line. After sorting out some relatively contained dependencies regarding ARTS and a couple of other packages, I got into the more open-ended stuff: error: Failed dependencies: python-qt = 3.5.0-7 is needed by kdebindings3-python-3.5.0-7 libpoppler-qt.so.0 is needed by kdegraphics3-3.5.0-6 valgrind >= 3.0.0 is needed by kdesdk3-profile-3.5.0-7 libdb-4.1.so is needed by kdevelop3-3.3.0-5 libqscintilla.so.6 is needed by python-qt-3.5.0-8 libakode.so.1 is needed by (installed) kio_burn-0.7-0.pm.0 I found updated packages for qscintilla, and got: error: Failed dependencies: libqscintilla.so.5 is needed by (installed) kdebindings3-python-3.4.2-8 I'm not sure what I'm looking at, here. Is the reference to "installed" merely telling me that I've already got a version that's installed and working (with KDE 3.4), or is this a pointed warning that if I upgrade libakode and libqscintilla, then KDE 3.4 is going to stop working.... probably before I've gotten as far as getting 3.5 to work... ?? Because of my undertainty, I'm rather afraid of running rpm -U with -force or -nodeps. Since I am very much a gui kind of person (I do use the command-line, but as an adjunct to doing all my everyday stuff via gui) I don't want to disembowel KDE 3.4.2b before I've got 3.5 installed and mostly working. What's the poop? Is there a way, other than trying it and having things break, to know if an app will accept a link to a newer version of a package as long as the link is named as the older version? Is this just a situation where I can create a couple of symlinks and everything will be happy again? Or .... what? I mean, I'd just try it, but this isn't one of those stand-alone things that you can try independently. This is all of KDE, and for all I know, most of the rest of my system. I've had experience of loading newer version packages and faking links to the older version in the middle of a bunch of interdependent packages and I ended up re-installing SuSE (I think it was 7.3) from CD because that was far easier than trying to fix all that I had broken. Kevin (not wanting to abandon the hundreds of MB of fine KDE packages he's already downloaded)