https://bugs.kde.org/show_bug.cgi?id=409120
--- Comment #3 from Nate Graham <n...@kde.org> --- I'm not asking you to use Discover, but rather `pkcon`. If you're not comfortable using that, then you shouldn't use Discover either, since it uses PackageKit. > I also think a better alternative would be to use aptitude and show all the > choices and changelogs to the user just in case. Sure, go ahead, if that's what you would prefer. However in Discover-land, we need to work with the sources of information we have available, which currently come from PackageKit, which gets it from the aptcc plugin. As you can see, by being distro-neutral, we expose ourselves to the situation where features that work when using the native package manager don't work when using PackageKit (and hence Discover). It would be theoretically possible for someone who write a dedicated Apt backend to Discover that doesn't go through PackageKit, which might offer a superior user experience by bypassing all these PackageKit issues. However this would be a ton of work, and would require that whoever did it to basically re-implement half of PackageKit but in a way that only worked for one distro family. So far nobody has stepped up to do that because it's so much easier to just use PackageKit. Ultimately, distros that want to offer a better user experience need to step up and do the work to better-integrate their package management systems with standard GUI software updater apps. -- You are receiving this mail because: You are watching all bug changes.
