Torsdag den 27. januar 2011 19:09:47 skrev todd rme:

I have been trying to use kpackagekit in place of yast for managing software in 11.4, and I have noticed that it seems to not do anywhere near as well resolving conflicts. For instance the updater does not seem exclude conflicting updates like YaST does. Rather than reporting the conflict and letting you handle it, or skipping the packages that can't be updated, it just fails. It seems a bit strange, I thought packagekit was just a front-end for zypper. Is this expected behavior?

It also won't let me ignore signature problems with repositories like YaST does, which prevents me from using the factory packman repo.

It is not _just_ a zypp frontend. KPackageKit is a frontend for PackageKit(d) which includes a zypp backend. So there are several layers which can (will?) have bugs. E.g. currently there's a bug in the zypp backend which means PackageKit performs vendor changes without hesitation or warning. PackageKit itself also has some limitations. I think it's just intended to cover the basic functionality which is common for all the major package management systems. It will never be as feature complete as a dedicated package manager like yast or zypper. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org