Maybe; I don’t know. But still the question remains: Does libzypp have support for it? I haven’t found anything.
The support might be there, but current policy/practice is to not include the Group: tag, when packaging, and it’s been like this since roughly 2019.
I know nothing I package/maintain has Group: tags, it’s not actually a particularly useful tag, since there’s no standardization or validation of it, to the best of my knowledge.
This is now not about RPM group tags anymore, it changed to appstream categories.
If there were support for it in libzypp, and if there were a meaningful number of packages that have those fields, I’d try to come up with some support for it in Myrlyn; maybe even as a fusion of the old RPM group tags for packages that still have them and appstream categories for packages that have them.
But without support from libzypp, I don’t think this can work.
1 Like
I used Mandrake, Mandriva and Mageia for decades. I loved the groups because I could look at all of the multimedia players or text editors etc.
It helped me discover new programs when I was new and didn’t know the name of everything.
It’d be very handy, especially for people who are new to Linux, to locate software that they already have and don’t know it.
1 Like
I fully agree, but please read the discussion in the linked GitHub issue in my original post here: The RPM groups in the packages’ meta data fell out of use long ago, and now they are largely removed or bit-rotted away.
2 Likes
Has anyone submitted a feature request to libzypp to support AppStream metadata?
Is that the policy for SUSE/openSUSE? It’s the policy for Fedora sure but that’s not what we are talking about.
There’s some standardization in (open)SUSE at least.
RPM Group’s and Appstream categories have some cross over but they aren’t the same. Altough aligning the former with the latter might work.