Bugzilla – Bug 227379
major flaws in dependencies
Last modified: 2007-10-10 17:26:45 UTC
Example: if someone likes to remove QQ_quickstarter she/he has to remove whole KDE! Gosh...
kdepim3-notes and other packages have the same problem (bad dependencies in yast).
This is working as intented. The quickstarter is an essential part of the KDE desktop. Klaus, this confuses users - what shall we do?
Wait, wait -- OpenOffice QuickStarter is so important _for_ KDE that KDE cannot run without it? In other words you cannot use Kmail without OOQS? Come on... Kmail and other KDE-apps can perfectly run without OOQS -- living proof, computer I use to write this reply ;-)
The full-blown KDE desktop contains OOo Quickstarter. You can use the minimal KDE base system as alternative... Please see the archives of the opensuse-factory mailing list for patterns and how they work.
Andreas, forcing uninstall kdenetwork when unistalling OOQS __does not make sense__. And I don't use full-blown or minimal -- thanks to package manager I can install exactly what I want. So there is flaw somewhere -- either in recognizing "pattern version" (max vs. minimal), dependencies, but there should be no such behaviour as described above.
Maciej, I understand completely what you're saying. The technical problem is that patterns have must-have dependencies, like the quickstarter, and removing that breaks the pattern. Now there are two questions: * Why is quickstarter a hard dependency, shouldn't it be soft? * Why do the other packages get removed as well? The second part is what puzzles and confuses you. I merely wanted to enlighten you about the technical background. The question here is what is the best way to handle this situation - and Klaus has to take care of it;-)
I ran into similar problems when trying to minimize a 10.2 installation. So I'm very well aware of the situation. But thats not fixable within a released product but to be targeted for 10.3
*** Bug 223675 has been marked as a duplicate of this bug. ***
Revisit in preparation of Code11
10.3 is a major improvement. Future steps to be discussed on opensuse-factory.
I spotted the same behaviour in 10.3. I already reported a solution how to avoid at least reporting such "problems".
PS. In other words -- 10.3 is improvement, yes, but this issue is not fixed.