On Monday 02 September 2002 18:01, Carl wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 02 September 2002 01:11 am, you wrote:
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.
That's actually a safer method than most people use. But supposedly with K in Supplementary, all dependencies are there.
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
Don't use -F or -I. Always use -Uvh to install anything. Most people go to the directory then rpm -Uvh --nodeps * . Ben recommends (and I do too): Install base then dev then apps. 1. After each installation of a group such as base you should run SuSEconfig. 2. After all three groups are installed you should remove these things... A. All KDE related directories and files in /tmp B. .mcop in your home directory C. The two temp files in .kde that are pointing to files that you've removed in /tmp.
Why is -F a bad idea? Do I misunderstand the rpm man page? It says that -F updates a package if a previous version is already installed. As upposed to -U which, as I understand it, updates no matter what. What good things do SuSEconfig do? (I didn't run SuSEconfig at all, and it seems to work fine just the same.) I didn't remove any of the things you suggest. What do I risc by leaving them? Thanks for a lot of good answers :o) Best regards Johnny :o)