Hi,
On 12/19/25 1:32 PM, Benjamin Beasley via ruby-sig wrote:
I am considering a PR by Vít Ondruch for cucumber-messages[1] that would build
rubygem-cucumber-messages as a subpackage rather than maintaining it as a
separate source package. I am generally inclined to favor the proposal, but it
seems to me that it represents an exception to the “MUST” requirement to
package RubyGem libraries from the released gem archives. I’ve therefore raised
the issue on the Fedora Packaging Committee tracker[3]. The purpose of this
email is to raise visibility of that issue among Ruby packagers, and to solicit
input from knowledgeable and interested parties.
As someone who updated the cucumber stack in Ruby before, and
considering they have multiple language specific variants,
I see this as a good step forward. This is a more complicated/complex
project, where we can achieve more efficient, less labor intensive
and more up-to-date software/library across programming languages in
Fedora if we build all parts from single source.
Especially for cucumber-messages that is templated.
Regards,
Jarek
[1] https://src.fedoraproject.org/rpms/cucumber-messages/pull-request/2
[2] https://docs.fedoraproject.org/en-US/packaging-guidelines/Ruby/#_rubygems
[3] https://pagure.io/packaging-committee/issue/1512
--
_______________________________________________
ruby-sig mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
