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.
/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 and rpm -Uvh *.rpm, and let rpm sort out the dependencies.
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. 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.
run SuSEconfig
Why? I've never run SuSEconfig when I install/upgrade KDE, and it works fine anyway. //Anders -- `When I use a word,' Humpty Dumpty said in rather a scornful tone, `it means just what I choose it to mean -- neither more nor less.'