Hello, I'd like understand how groups of package are now detect , specially in 3rd repo packages which can't use comps.xml. Thanks ! -------- Forwarded Message -------- From: Sérgio Basto <sergio@xxxxxxxxxx> To: packaging@xxxxxxxxxxxxxxxxxxxxxxx Subject: Re: [Fedora-packaging] Re: why the Group tag is obsolete ? Date: Sun, 28 Aug 2016 07:24:58 +0100 On Seg, 2016-08-01 at 09:17 -0600, Dave Johansen wrote: > > On Sun, Jul 31, 2016 at 9:23 PM, Sérgio Basto <sergio@xxxxxxxxxx> > wrote: > > > > Hi, > > A year ago, I learned that Group tag is obsolete [1] I remember ask > > the > > reason and is something about comps.xml that I don't remember > > neither > > find on google , but for projects that still use repoview, Group > > tag is > > needed. So the questions are, have we any replacement for repoview > > ? or > > another way to show one repo content ? and why the Group tag is > > obsolete ? can someone remind me why. And how we now the group of > > one > > package ? . > > > > Thanks. > > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1239067#c1 > Here's the FPC ticket about it: > https://fedorahosted.org/fpc/ticket/199 ; Thanks I was able to find the reason: RPM in Fedora 18 does not require the presence of the Group tag in the spec file. If the tag is defined, it will be ignored. The package groups of the yum application are used on a Fedora 18 system as the relevant source of information on which group is the package a part of. I remembered in one thread of devel mailing list on create hawaii group and bingo found the link: https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_groups So now, how I know the group of the package (via yum or dnf) ? seems to me many packages will not have group ... and 3rd-part software ? Also /usr/bin/gnome-software how find the group of the package ? Well this is not a very important matter , but I'd like try organize packages in groups , via repoview. Thanks. -- Sérgio M. B. -- Sérgio M. B. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
