On Thursday 31 August 2006 18:52, Carl Hartung wrote:
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.
Well, I knew from earlier use of an apt-based distro that if you forced in a package by ignoring predefined deps that it basically made the package manager unusable until the unresovled dep issue was resovled. I was not aware of being able to set or reset ignored conflicts in YaST. If this could be done on a per package basis then that would present a different (though probably not recommended) way to maintain these type of packages. -- /path/to/Truth