[packagekit] PackageKit Collections.

Anders F Björklund afb at algonet.se
Sat Sep 13 01:59:56 PDT 2008


Tim Lauridsen wrote:

> The idea was to handle the yum groups as metapackages shown in the gui
> in a special 'Collections' group.
>
> if you select the Collection you will see all yum comps groups as
> metapackages there can be install/removed/updated.

I've added the "Package collections" to the Smart backend now,
for the "Virtual" groups of Yum comps and the YaST2 patterns:

     # Yum
     'Virtual'                                 : GROUP_META_PACKAGES,
     'Virtual/Applications'                    : GROUP_META_PACKAGES,
     'Virtual/Base System'                     : GROUP_META_PACKAGES,
     'Virtual/Desktop Environments'            : GROUP_META_PACKAGES,
     'Virtual/Development'                     : GROUP_META_PACKAGES,
     'Virtual/Languages'                       : GROUP_META_PACKAGES,
     'Virtual/Servers'                         : GROUP_META_PACKAGES,

     # YaST2
     'Virtual'                                 : GROUP_META_PACKAGES,
     'Virtual/Base Technologies'               : GROUP_META_PACKAGES,
     'Virtual/Desktop Functions'               : GROUP_META_PACKAGES,
     'Virtual/Development'                     : GROUP_META_PACKAGES,
     'Virtual/GNOME Desktop'                   : GROUP_META_PACKAGES,
     'Virtual/Graphical Environments'          : GROUP_META_PACKAGES,
     'Virtual/KDE Desktop'                     : GROUP_META_PACKAGES,
     'Virtual/Server Functions'                : GROUP_META_PACKAGES,

This requires the modified "groups" branch of Smart to work,
it is available from https://launchpad.net/~afb/smart/groups

--anders

PS.
Actually it will sort _any_ comps/patterns into META_PACKAGES,
including the ones you've added yourself, based on the "parent":
to handle the openSUSE RPM groups, I added a group check to test
for a "Foo" group should the "Foo/Bar" subgroup not be defined...




More information about the PackageKit mailing list