<br><tt><font size=2>Tim Lauridsen wrote on 09/11/2008 18:15:15 +0200:<br>
<br>
> He had a little discussion on irc today, about how to support yum
groups <br>
> and other similar type of groups in other backend types.<br>
> <br>
> The idea was to handle the yum groups as metapackages shown in the
gui <br>
> in a special 'Collections' group.<br>
> <br>
> if you select the Collection you will see all yum comps groups as
<br>
> metapackages there can be install/removed/updated.<br>
> <br>
> In the api installPackages etc are extended to handle meta packages<br>
> <br>
> ? meta package id is just like an normal package id but with a special
<br>
> keyword instead of a repoid. it could be [meta] or ~meta.<br>
> <br>
> if a backend dont support this then it just dont return any members
for <br>
> the collection group (GROUP_META_PACKAGES).<br>
> <br>
> Let me know what you all thinks.<br>
> <br>
> Tim</font></tt>
<br>
<br><tt><font size=2>Hi Tim</font></tt>
<br><font size=2 face="sans-serif">I started to detail the use case for
a PackageKit API for yum groupinstall in this bugzilla ticket:</font>
<br><font size=2 face="sans-serif"> </font><a href="https://bugzilla.redhat.com/show_bug.cgi?id=435768"><font size=3 color=blue><u>https://bugzilla.redhat.com/show_bug.cgi?id=435768</u></font></a><font size=3> </font>
<br>
<br><font size=2 face="sans-serif">A special Collections group / metapackages
in the gui would be fine. We also want to install the yum groups
via a dbus call or an API call.</font>
<br>
<br><font size=2 face="sans-serif">-- John Walicki</font>
<br>