On Thu, 6 Apr 2006, Robinson Tiemuqinke wrote: > Panu and all, > > Thanks a lot for reply. I've see a lot of helpful > geniuses here... > > My new question is: how to show the packages defined > in my own custom groups with a format similar to FC4 > distro's comps.xml file? > > 'yum groupinstall <my_own_group>' works perfectly, > while 'yum groupinfo' shows only enclosed group names, > not packages in the enclosed groups. Mm.. I don't see anything obviously wrong in your groups file, unless the lack of <description> tag causes somehow the packages not to be listed but I can't imagine that being the case :) Note that packages from groups required by a given group are *not* shown in groupinfo, only the immediate <packagereq> packages from the group itself you're groupinfo'ing about. > > I've tried to run 'repoquery -l -g <my_own_group>', > but this time even worse: it reports no output at all. > although 'repoquery -l -g core' and 'repoquery -l -g > base' reports all packages inside. Repoquery uses the same exact code for getting the group information as yum itself, the only difference is how it's presented. One notable difference in presentation is that -l only lists the "contained packages", not the groups. To get group depenencies use --requires -g <somegroup>. Yes it's a bit arbitrary... > [root@testnode01 tmp]# repoquery -l -g 'Example Custom > Install' > [root@testnode01 tmp]# > [root@testnode01 tmp]# repoquery -l -g 'Mail Server' > [root@testnode01 tmp]# > > Oh, it seems that the argument to -g option should > ONLY be a single word? Yup, repoquery only understands the group id whereas yum itself accepts both the name and the id. That's kinda deliberate because I just seriously dislike spaces in names, kinda like you'd install/query rpm's by their summary text instead of the package name :) - Panu -
