Changes between Version 1 and Version 2 of NoDeps

skvidal (IP:
09/30/10 18:47:49 (7 years ago)



  • NoDeps

    v1 v2  
    1010 * --nodeps is only used when a package or system is badly broken. As a general rule if you find you cannot put the screw in the hole with a screw driver you should not go get a hammer.  
    1111 * --force tells rpm - if there are any pkg or file conflicts just blow them all away with what I'm giving you. Again - not a good idea if you want to keep your system running well. It's like gardening with a backhoe. 
     12 * When you go to update yum relies on an assumption that the rpmdb is roughly correct. We've added functionality to warn you when we notice your rpmdb does not have dependency closure - but it is likely that using --nodeps and --force will screw up updates. 
    1314If you find you have no way out and you NEED --nodeps and/or --force - well - this is why they are available in rpm.  
    1415If you are knowledgeable enough to know you need ignore dependency resolution and force the files into place then you should also be knowledgeable enough to know how to use them with rpm. 
     18What to use instead: 
     19 * yum shell: the yum shell will let you remove pkg1 and install pkg2  in a single transaction so you don't have to use --nodeps as a hold-over to swap two conflicting pkgs out 
     20 * yum reinstall: if you just need to reinstall all the files of an installed pkg just use yum reinstall 
     21 * yum downgrade: gotta go back to an older version of a pkg b/c the new one is broken? Yum downgrade can do that. 
     22 * package-cleanup: package-cleanup is a yum-util to help you sort out what things might be terribly wrong with your system