Changes from Version 1 of NoDeps

skvidal (IP:
09/30/10 18:42:04 (8 years ago)



  • NoDeps

    v0 v1  
     1= Nodeps and Force = 
     3Rpm offers command line options --nodeps and --force. They are intended to allow the admin to put pkgs in place despite conflicting files, unresolved dependencies or just about anything else. 
     5Yum does not implement these options in any way due to the destructive nature of what these options are capable of doing. 
     8Why are --nodeps and --force bad for yum: 
     9 * yum is a package manager and automatic dependency solver. if you use --nodeps it is no longer solving dependencies it is the equivalent of rpm2cpio except it is also updating the rpmdb with broken information 
     10 * --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.  
     11 * --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. 
     13If you find you have no way out and you NEED --nodeps and/or --force - well - this is why they are available in rpm.  
     14If 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.