[packagekit] Listing all packages
Thomas Wood
thomas at openedhand.com
Wed Jan 16 15:08:33 PST 2008
On Wed, 2008-01-16 at 21:49 +0000, Richard Hughes wrote:
> On Tue, 2008-01-15 at 14:51 +0000, Thomas Wood wrote:
> > >> GPS -> ??
>
> What about GPS? Software or maps or what?
Well, since there is a separate Maps section below, I'm guessing this is
just software.
>
> > >> Sources -> ??
>
> We need "repos" for this, as the source name is very overloaded with
> development packages.
>
> So, can I add for now:
>
> PK_GROUP_ENUM_COMMUNICATION
> PK_GROUP_ENUM_NETWORK
> PK_GROUP_ENUM_MAPS
> PK_GROUP_ENUM_REPOS
Looks good, this will definitely help us.
>
> > "Sources" is apparently the same thing as repositories. The repository
> > management is going to be done using packages because ipkg doesn't
> > implement any repository management functions itself, and this will be
> > the easiest way for users to download and "install" new repositories.
>
> Sure, livna and stuff does the same in Fedora.
>
> > Sounds good, but how would the custom filter be defined? I don't want to
> > add vendor specific code into the backend, so the filter rule must be
> > passed in at configure. Or is there another way?
>
> Hmm. Okay, what about we make the filter called "visible" and we only
> implement that filter if we want control over the output options.
>
> Okay for me to add PK_FILTER_ENUM_VISIBLE?
That definitely sounds like a better option than before. I guess the
idea is to limit the visible packages to ones relevant to the end user,
so I don't know if it makes sense to use that description for the enum
at all?
Regards,
Thomas
--
OpenedHand Ltd.
Unit R Homesdale Business Center / 216-218 Homesdale Road /
Bromley / BR1 2QZ / UK Tel: +44 (0)20 8819 6559
Expert Open Source For Consumer Devices - http://o-hand.com/
------------------------------------------------------------
More information about the PackageKit
mailing list