I am member of Fedora ruby-packagers-sig and I found myself entrenched deeper in the Ruby side of Fedora, recently taking over part of introducing the new Ruby version.
The main reason for this request is to smooth out the process with updates on, mostly, packages using or extending Ruby via dynamic library. I have partially taken over the development of Ruby from @vondruch . Update to a new minor release usually brings many changes and bumps soname. This then involves rebuilds & sometimes also fixing of >= hundred of (mainly) rubygem packages. Such packages may or may not have ruby-packagers-sig attached, as it is up to the main package maintainer. As such, proven packager rights would aid in (re)building packages in a side tag and more easily fixing them when necessary.
Apart from Ruby itself I also manage the rubygem-cucumber stack, vagrant (and Ruby virtualization library bindings necessary).
I have been a fedora contributor for some years at this point and a member of the Ruby SIG also for several years.
Would it help instead if the ruby-sig was added automatically to all ruby- packages, similar to how this is handled for rust-, ghc-*, and golang-dependent packages?
Would help for some. However, non-rubygem packages make nontrivial portion of the binary dependants, like swig, libselinux, dnf5, ...
$ dnf repoquery --disablerepo='*' --enablerepo=rawhide --enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel' | sort | uniq | grep -v rubygem | wc -l 47 $ dnf repoquery --disablerepo='*' --enablerepo=rawhide --enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel' | sort | uniq | grep rubygem | wc -l 69
almost 50 packages, among which are for example alexandria, swig, libselinux, graphviz, subversion, (looked it up just now, this is next month's problem for me :) ).
So unfortunately it would help only partially.
+1 for @jackorp
While this would partially help, I am not fan of this approach, because it makes the packages look like they are somehow magically maintained when they are not.
This request needs to be announced to the sponsors (email sent to packager-sponsors AT fedoraproject.org)
+1 as a sponsor
I've sent the email to packagers-sponsors.
+1 from me.
+1
APPROVED (+8,0,-0)
Metadata Update from @fale: - Issue tagged with: pending announcement
Metadata Update from @fale: - Issue untagged with: pending announcement
Metadata Update from @fale: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
@jackorp has been added to provenpackager
Log in to comment on this ticket.