KPackageKit issues

[Kevin Kofler]

Hi,

a few things I noticed in KPackageKit under Fedora (but they affect all 
distros):

1. KPackageKit keeps forgetting its settings and we can't figure out why. See 
this Fedora bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=475303
The thing is, in Fedora, we DO NOT want KPackageKit to automatically install 
updates, it should always prompt the user. Yet, we tried:
* setting a default option in kde-settings and even
* patching the code to default to NONE instead of SECURITY everywhere:
http://cvs.fedoraproject.org/viewvc/rpms/kpackagekit/F-10/kpackagekit-0.3.1-defaults.patch?revision=1.1&view=markup
(by the way, I think you should consider also changing this upstream - 
installing updates without asking the user is extremely rude!)
and yet it still somehow magically resets to SECURITY at random times. :-( 
Moreover, when it does that, it also installs non-security updates, so 
apparently it really resets to All, not Security only. The UI displays the 
magically-changed setting as "Security only" though.

I tried looking at the code to search for the bug, but I still have absolutely 
no idea what is happening. :-(

I consider this an absolute showstopper, so the sooner it is fixed, the 
better! Do you have any idea what could be up there?

2. In KpkNotify::updatesActions, you do this:
	    if ( packages.size() <= 5 ) {
		// we already show the user all the packages to be updated
		Client::instance()->updateSystem();
	    }
	    else {
		emit showUpdatesUi();
	    }
Can you please change this to just emit showUpdatesUi();? For 2 reasons:
* Consistency - having the "Update" button do something different at different 
times is surprising and can lead the user into doing the wrong thing 
(installing updates when they actually just wanted to review them).
* The user may want to review the update details. You "already show the user 
all the packages to be updated", but not the details (i.e. update 
description, Bugzilla references etc.). Some users (e.g. me!) want to know 
exactly what they're updating before accepting the update!

3. This is more an annoyance than an issue, but it would nice if the sorting 
of the updates were improved:
- more important updates should be listed first, i.e. security before bugfix 
before enhancement
- within the same type of updates, alphabetical order instead of the current 
random order would be nice
Likewise, alphabetic order would be nice in the search results for new 
packages.
If this is just not implemented yet and you don't have the time to implement 
it, any objections to me working on it and committing the result to KDE SVN?

        Kevin Kofler