Hi <snips>
That seems to work, and the updated KDE 3.0.3 comes up and runs just nicely (as far as I can see).
It was a bit of a hazzle though to make sure to update the KDE dependencies.
But I did like this with every package:
First i rpm -U (No --nodeps)
If the package was updated without dependency errors, then fine.
If there were dependency errors, I would note the dependencies and rpm -U --nodeps the same package again, and then go on to rpm -U the dependency packages - same scheme.
I wonder. If I have a whole slew of packages installed that I want to update, and I'm not sure what packages those are, could I then update all installed packages in one command like this?:
rpm -F --nodeps *.rpm
Or perhaps...
for package in *.rpm; do rpm -F --nodeps $package; done
Would that update only the packages that are already installed?
If you are able to get all the packages into one directory and run rpm -F over them, you shouldn't need the --nodeps. If you get any, try to satisfy them rather than over-riding them, i.e. obtain the rpm the complaint is a bout and add it to the directory. This has worked well for me for several updates, and yes using -F for freshen does mean only the installed packages are freshened, any others you may have in the directory are ignored and should cause you no problems. This serves me well, but not everyone seems to have success with it. Give it a go, though, as it should be safer than using --nodeps.
By the way. The rpm man pages shows a '+' after the package name, but I can't see anywhere what that's for. I don't use the '+', and it works anyway.
What's the '+' for?
Dunno ... HTH Fergus