[packagekit] Changing the Package signal to include a type

[Richard Hughes]

On Tue, 2008-03-04 at 13:36 +0100, Tim Lauridsen wrote:
> Richard Hughes wrote:
> > After my talk at FOSDEM I got talking to the suse guys about other types
> > of package, such as deltarpm and binary patches. We don't want to treat
> > these any differently, but we might want to display a different icon in
> > the UI or have different update policy based on the update type.
> > 
> > In the yum and yum2 backends we also emit a signal called MetaData which
> > we don't actually do anything with. It would be also useful to push this
> > in to the Package signal so we don't have YAS (yet another signal) and
> > still can get feedback into the UI about what we are doing.
> 
> The MetaData signal is not releated to a package, it is send when the 
> yum backends download differnt kind of metadata.

Sure, I'm a little uncomfortable with this myself, as it's not a status
call, and not really a package call either.

> It is a little hard for me to see the use of this, do you girlfriend 
> care if it is a deltarpm or a full rpm an update is an update.

Well, it's designed more for a corporate users than my girlfriend,
perhaps this was a bad example. On suse you might want to automatically
install patches but not new packages.

> We should take care not to add to many distro / backend specific options 
> to the API.

Sure, comment heeded.

Richard.