[packagekit] PackageKit Collections
tim.lauridsen at googlemail.com
Sun Sep 14 01:08:19 PDT 2008
Richard Hughes wrote:
> On Sat, 2008-09-13 at 14:05 +0200, Anders F Björklund wrote:
>> I have a problem with the above approach, and using repoid for this...
>> Currently I have the same metapackage appearing in two package channels,
>> say for instance fedora and fedora-updates - each with their own comps:
> Right, so this scuppers using the data part of the package_id as a type.
>> Now, if I replace the repo with '[meta]' then I now get two identical
>> package_ids whereas before they would differ in their "data" section:
>> This is not good, since the package_id in PK must be unique for each ?
>> And if I remove a dupe, then I'm not sure which one the id refers to ?
> Exactly, the PackageId _must_ be unique.
>> Is there somewhere to store the "is-a-meta-package", outside the
>> repoid ?
> I think adding new info enums might be the best plan, something like:
Do we need these, INFO_INSTALL and INFO_AVAILABLE if fine.
> This also lets us trivially use the icon theming too.
> We'll also need a new filter enum to filter out (or in) the meta
> packages. Something like PK_FILTER_ENUM_META_PACKAGES or
> PK_FILTER_ENUM_COLLECTIONS might be the best plan. Better names welcome.
we are using GROUP_META_PACKAGES to get the meta packages.
./yumBackend.py search-group none 'meta-packages'
will show all the meta packages.
.yumBackend.py install-packages 'kde-desktop;meta;meta;meta'
will install the metapackage 'kde-desktop'
.yumBackend.py remove-packages no 'games;meta;meta;meta'
will remove the metapackages 'games'
.yumBackend.py get-requires none 'games;meta;meta;meta' no
will return the requirement of the packages and deps of the 'games'
this work in the current yum backend in git, what else do we need ?
> PackageKit mailing list
> PackageKit at lists.freedesktop.org
More information about the PackageKit