On 17/10/2019 16:15, Matěj Cepl wrote:
2. Because of #1, for most package maintainers Group label is nothing anybody cares about. It used to have to be filled with something which gets through rpmlint and that’s how far most package maintainers IMHO cares.
3. Given #2, groups are such mess, no user uses them for searching for their software, because nobody knows whether Network Manager is in Productivity/Networking/General, System/Networking, or something else. See below on problems with tree hierarchies.
Yes the only problem with groups is the actual groups that were created, there's no attempt to fix the actual problem (except for Jan) just an unwarranted attempt to obliterate the tag in spec files. In fact I've just built ffmpeg-4 with a local rpmbuild using the line in the spec file: Group: Productivity/Multimedia/Video/Editors and Convertors:Multimedia/Audio/Editors and Convertors This is now present in the GROUP tag within the rpm that was generated. This means that the Group: tag in the rpm can also be used for multiple tags as proposed by Jan. Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org