On Tue, Jun 25, 2002 at 04:17:57PM +0200, Anders Johansson wrote:
On Tuesday 25 June 2002 13.49, Jon Clausen wrote:
Hopefully you put the files you downloaded into a structure like this: Stuff from the /base in /some/path/base /dev in /some/path/dev
You don't actually need the devel packages unless you intend to compile things. They are not needed for the everyday use of KDE.
True. This would be the generic approach, and I'm not about to argue with whoever recommended this sequence to me. Obviously they know this *way* better than I'll ever hope to. But yeah you don't need dev, if you're not going to compile stuff... Let Eddie decide what *he* needs.
/apps in /some/path/apps
Also, I don't see the point of separating the rpms into different directories if you're going to install the lot anyway. Put everything you're going to install into one directory
Maybe separation is a nonissue. Maybe it's to do with apps depending on dev/base, and dev depending on base, and it makes sense installing in that sequence? *Even* if you --force...
and rpm -Uvh *.rpm,
If you *have* downloaded the lot, it could be kind of laborious to verify which rpms were already installed. So how about using -F instead?
and let rpm sort out the dependencies.
Which was already tried, and reported to fail. Am I mistaken in that dependencies *will* fail in this situation, because of catch 22?
If you have that structure, then in that order (base, dev, apps) do: enter directory rpm -Uvh --nodeps --force *.rpm
Don't use --nodeps --force unless you're very, very sure of what you're doing.
Certainly. When I upped KDE, it didn't much matter to me anyway, because I hadn't fully moved from 7.3 - it did, however work quite nicely. Also, I could have missed it, but I don't recall any problems reported as a result of this way to upgrade kde...(?)
Especially --force could end up overwriting files you don't want to be overwritten. Don't rely on the package maintainer being infallible. If there's an error, it's probably a good idea to try to find out what the error means.
Always. Though from what I understand from the messages about this topic, the errors basically amount to catch 22. But sure, stuff can go wrong. Hence my "words of warning"... back up your .files, check ownerships/permissions afterwards. Certainly something *did* sort of, kind of go wrong for me. But if the worst that happens (my experience) is that some files end up being owned by root, it's not really that bad... I hope it didn't come across as if I was saying "If it won't install, just --force it <yeehaw>" because that's certainly not how I meant it. What I meant was, that in this particular case I've had success with it myself, and I'm not aware of anyone experiencing problems...
run SuSEconfig
Why? I've never run SuSEconfig when I install/upgrade KDE, and it works fine anyway.
Why not? cheers, Jon Clausen