[sorry, meant to go to list] > imho "rpm -Uvh *" won't work for two reasons:- > > 1) There are _hundreds_ of dependency errors because that command will > attempt to install the rpms in alphabetical order, and..
IMNSHO that is BS. rpm will resolve all dependencies of all the packages on the command line together with what's installed irrespectively of the order with which the packages are specified on the command line. You only have to make sure there is only one invocation of rpm, i.e. specify *all* packages on the command line. > 2) There will be _hundreds_ of conflicts with the existing kde > applications you have installed. I don't think this is true either. The existing packages are "old", therefore their dependencies will disappear. > My personal experience with the rpm system is that you surrender control > of your computer to the builder of the rpm This is no different to apt. Besides, it's not true. rpm will not install new packages if one of their files conflicts with the same file of another already installed package, unless that package is updated to a newer one with the same invocation. Tell me how that can screw your system in a hurry (assuming that's what you mean by "surrender total control")? And, don't forget, we're not talking about nuking existing kde 2.x packages being a propblem here - that's the intent, not the danger. It is however a good idea to quickly check -qp --scripts <package>. > ( who may or may not be > competent ). Very true. As for competence, I have to say yours about rpm isn't that great... :-) I don't like people spreading this FUD about rpm. Let me guess - you use debian? Nobody has yet mentioned the real reason why dependecies are a pain when it comes to installing foreign-distro packages, and why rpm -Uvh in this case has a good chance of a big barf (in which case use --nodeps and hope it works). Volker -- Volker Kuhlmann, list0570 at paradise dot net dot nz http://volker.orcon.net.nz/ Please do not CC list postings to me.
