[packagekit] PackageKit Collections

[Anders F Björklund]

Tim Lauridsen wrote:

>>> 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:
>>>
>>> 'fedora-packager;0;noarch;[meta]'
>>> 'fedora-packager;0;noarch;[meta]'
>>> 'fedora-packager;0.3.0-1.fc9;noarch;fedora'
>>>
>>> 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.
...
> .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'
> metapackage.
>
> this work in the current yum backend in git, what else do we need ?

How do you separate the metapackages (comps) in one yum repo,
from the metapackages available in another repo ? Since each
"repodata" has their own definition of comps bundled, I mean.

--anders