https://bugzilla.novell.com/show_bug.cgi?id=215649 ------- Comment #19 from benji.weber@gmail.com 2006-10-30 21:26 MST ------- Andreas, No-one wants a repeat of 10.1 through lack of testing (your fear), But equally no-one wants a repeat of 10.1 through being so afraid of change all the problems of 10.1 are allowed to remain. 10.1 remastered shows what your scenario with ZMD remaining gives, it is better but the underlying issues remain. 10.2 needs to be done right. You seem to be under the impression that a new untested architecture is being proposed here, that is not so. Instead the suggested course of action is the removal of part of the existing architecture that has proven to cause problems. ZMD does not provide extra protection against bugs in zypp. The YaST <-> ZMD synchronisation was and always will be a hack. You are claiming that the ZMD based tools are more tested than YaST/YOU based directly on top of libzypp. In fact they have both been used for as long, and the zmd based tools are not even capable of updating vanilla 10.1, so in fact yast package management has been tested more. The only new things in question are the opensuseupdater and zypper. when using the libzypp backend directly opensuseupdater does little more than notify of updates and launch YOU. Zypper is somewhat more experimental but also less of a concern. The primary concern is that the tools that inexperienced users will see. If ZMD were dropped KDE users would be relying on YOU for updates, and a new tray notifier to let them know there are updates available (as all other versions). So what is the worst that could happen from using the "untested" opensuseupdater (as this is what seems to concern you). Worst case: users don't get notified of updates, they will still be able to get them provided YOU is working. If ZMD is not dropped then we still have the hacky architecture that has proven to cause problems for the past 8 months or so. Every change to either zypp or ZMD potentially introduces new edge cases which cause bugs that stop any of the update system from working. Testing is not a solution to a broken architecture. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.