> > I don't think I understand what you mean by "circular" dependencies. If > two rpms depend on each other, install both at once.
"Install both at once" ? This isn't always reasonable, if you have two rpm packages and one depends on the other to be able to install how do you install both at once? Even if you use rpm -Uvh * one gets installed before the other. In this case --nodeps lets you install each and the program will have it's dependencies once both packages are installed. This was the main problem I was running in to with the KDE rpms. Like I said though, everything is running great so --nodeps wasn't detrimental in my case. > > I, for one, can say that I do know what I'm doing, and I _never_ break > dependencies on a production machine. I just don't see the point of not > solving them. As for a "production machine" I prefer to compile everything from source. I didn't compile kde from source because it's a hog to compile. Almost every other software I use, unless source is not offered, I will compile it to know that I have more control over the installation. And plus i'm an uber geek and I just want to do stuff the hard way! Brad B
