[packagekit] How async is to async?

[Ken VanDine]

Some operations really shouldn't have to wait for other operations to
finish, and really causes pain for the end user.  For example, searching
shouldn't get queued up behind an update job.  The only thing that
should cause a search to get queued is if the cache is refreshing, and
if it does get queued we should give the user some obvious cue that they
have to wait for the result, and why.  And if the user searchings for a
package, and chooses to install it will just get queued up behind
whatever job it needs to.

Same goes for retrieving details and description related things.  Those
should just get serviced when they are needed.

Opinions?

--Ken