On Wed, 17 Dec 2003, Clif Smith wrote: > This is a little off topic as I'm dealing with Redhat 2.1AS in this > scenario, but please read on. If I have all of the rpm's as well as the > rpm's they depend on that I want to install to tailor and/or upgrade a > base install, is there any reason why I shouldn't do a rpm --nodeps vs. > letting yum or apt handle dependencies? Here's my scenario - I build > systems to QA my company's software. In doing so, I need to be able to > build systems using the exact versions of software we support. So, I > keep all rpms I install and/or upgrade in a share per each release of > our software. Currently, I just do a rpm --Uvh --nodeps to allow the > packages to be installed, knowing I'm installing the necessary > dependants, but possibly not in the "correct" order. You should never use --nodpes unless you can explain in detail why you need to. If you are building rpms that are broken they should be fixed. If you insist on installing rpms with --nodeps or --force it will eventually cause problems. Stuff will mysteriously stop working etc. The rules are the same for any rpm based system. There is a reason why yum etc. does not even offer the ability to do --nodeps or --force. Just courious why do you want to do this?? .................Tom
