On Tue, Jun 4, 2019 at 9:08 AM Igor Gnatenko
My name is Igor. I'm long-time contributor in Fedora and started
recently to contribute to the openSUSE with focus on cross-distro
collaboration. I'm also contributor to many upstream projects which
You can see my oSC19 talk here:
There are still few things which are different between Fedora and
openSUSE spec files for rust packages, more specifically those are
license header, Group tag and changelog. While license header and
changelog things are not easy to fix, the Group one is.
In Fedora, we have removed all Group tags in F30:
Groups are hard to choose (I would rather prefer to see some kind of
tags), there is no check from RPM itself (it is basically free-form
text field) and usually you can't put application into one group
because they belong to multiple groups.
I'm actually not a fan of the fact Fedora doesn't use the Group tag.
It's more or less a cop-out to not provide some kind of way to
organize all the packages in some manner. The fact that Fedora is the
*only* distro that doesn't use it speaks more to the fact that YUM
historically did not expose a way to sort using that tag. DNF does,
and frontends like dnfdragora can use it to sort.
I'd rather re-introduce a better formulated Group tag in Fedora, but
that takes some time I don't have right now...
I spoke to a few people on the oSC and it seems that
only YaST is
using this information to generate UI. So it should be doable to
change its representation which is not based on the Group tag.
Considering above, is there some process like Fedora Changes
) in openSUSE where I
can propose this?
Basically the way to do this is break everything by making submit
requests to delete it from everything, update the rpmlint policy to
flip from requiring a Group tag to requiring it to be eliminated, and
真実はいつも一つ！/ Always, there's only one truth!
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org