On Thursday 31 August 2006 19:21, Mike McQueen wrote:
On Thursday 31 August 2006 17:33, Carl Hartung wrote:
Using '--nodeps' isn't a good idea unless you know exactly what you're doing. It's better to run a trial, first:
# rpm -ihv packagename.rpm --test
If a person was to install an RPM with nodeps would YaST or ZMD then complain going forward anytime that you wanted to use it for package management (assuming there were some deps which were ignored), or would YaST simply accept the package with the conditions you passed it and not consider it a breakage?
It depends on whether or not the package actually introduces conflicts or has unmet dependencies. If there's nothing to 'complain' about, I don't imagine you will see anything unusual the next time you run YaST2. It *does* properly register the installed files in rpm's database, but I don't know off-hand if it sets the package's 'don't complain' flag in the process. In any event, in YaST's 'Software Management' module somewhere in the top menu, exists an option to reset previously ignored conflicts. That would be worth checking out. Think of the '--nodep' flag as something a developer might use to temporarily override normal protections to quickly test a code change or one that an 'expert user' might use during a series of out-of-sequence, interrupted or incremental changes. Carl