I noticed that urpmi now tries to figure out all the unresolved dependencies on your system just like how apt does. I think this is extremely annoying behavior and I wish I was disabled by default.
Justification: I have an application, SuperFoo, installed. It has a dependency on IBM's Java Runtime Environment (JRE). I need to use Sun's JRE because IBM hasn't bothered to release one that likes gcc 3.2 yet. And I know from my usage that it works fine with Sun's JRE. SuperFoo is a proprietary application so I don't have the source for it. Having to repackage it every release to remove the stupid hard requirement on IBM-JDK is extremely annoying. So I can install SuperFoo with straight rpm -Uvh --nodeps. Life is good and I can use SuperFoo. Now being the good Cooker person that I am, I do 'urpmi --auto-select' to sync with the latest packages. The latest urpmi says "Hey, we have unresolved dependencies! I MUST uninstall SuperFoo!", even though SuperFoo has nothing to do with all the other packages that I will be updating. I hope you see where this is painful. Every time I want to update Cooker, it will try to uninstall SuperFoo even though there is no reason to. Previously I have bragged to Debian users that urpmi is smarter because it only concerns itself with the packages that are being installed/upgraded. Please tell me there is hope that urpmi can be made smart again? -- Steve Fox http://k-lug.org
