On Tuesday, November 29, 2011 4:41 PM, "Martin Schlander"
Tirsdag den 29. november 2011 10:23:05 skrev Duncan Mac-Vicar P.:
PackageKit is just a dbus service that talks to ZYpp
Blame your YaST team, because we haven't had time to rewrite the glue between PackageKit and ZYpp and the current code is a mess or because we haven't finished making ZYpp lock-free for some operations.
But don't blame PackageKit.
But PackageKit builds on an assumption that the backends are working >:-)
If we had a proper zypp based updater there wouldn't be 3-4 different parties involved - where each one has the potential to severely hurt the distribution.
... and has done so consistently for as long as we have had packagekit based updaters. Despite all the effort that tgoettlicher, Will, yourself and others have put into this experiment trying to make it almost work for every release.
Packagekit is based on zypp though, that's the whole point - it uses each distribution's native packaging system. It provides a common interface so people building things like update programs don't have to re-invent their own interface to zypp, yum, apt or whatever. Maybe a start-from-scratch build of an updater would be better, or maybe it would just get into the same issues with zypp locking and all the other complexities of interfacing with zypp. Who can say when no other decent update program seems to be available?* *The online updater in YAST is no good as every user has to remember to start YAST and run it manually every day. Tim -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org