ruby-sig December 2019

ruby-sig@lists.fedoraproject.org

4 participants
6 discussions

Ruby 2.2
by Vít Ondruch 25 Jan '22

25 Jan '22

Hi everybody, Since Ruby 2.2 is going to be released during Christmas and -preview1 release is imminent (this Wednesday?), it is probably time to start looking into its packaging. So here is the updated .spec file [1] and scratch build [2], which can be finally build on all platforms. Sorry, no Copr for you, since Ruby's build fails there due to old RHEL kernel :/. What has changed from packaging point of view? Luckily, not much, but here are a few bullets which comes to my mind: * RPM 4.12 introduces new %load function, which is used to load RPM macros during RPM build. This allowed to drop my custom RPM macro [3]. On the other hand, you'll be able to build the Ruby only on F21+ (luckily, you should be able to build SRPM everywhere). * The RubyGems filesystem was not explicit enough, so there might be something accidentally packages. This is now more explicit, so we should be safer. * Ruby now ships with MiniTest and Test::Unit. The very good news is that they are installed so far as a regular gems. This means that you have to always specify them in your Gemfile, if you are using Bundler, but this is generally step in good direction. I hope that upstream will not change their mind :) Due to this change, we have new subpackages rubygem-test-unit (and rubygem-power_assert, which is now Test::Unit's dependency). No more %{_bindir}/testrb (but nobody is using it these days anyway, right? ;) * Some prevailing test failures were resolved, some others introduced, but hopefully they'll get resolved prior stable release. Generally, I'd say that not much has changed since 2.1, which is good news. Please test the packaging if you can and let me know about any issues you encountered. Also, if you have any other suggestions about Ruby packaging in general, what we could improve etc, this is probably good time to share. It seems that OpenSUSE guys are improving their packaging, so you might want to get some inspiration there [4, 5, 6] ;) Vít [1] http://pkgs.fedoraproject.org/cgit/ruby.git/log/?h=private-ruby-2.2 [2] http://koji.fedoraproject.org/koji/taskinfo?taskID=7578843 [3] http://pkgs.fedoraproject.org/cgit/ruby.git/commit/?h=private-ruby-2.2&id=8… [4] https://build.opensuse.org/package/show/home:darix:ruby/ruby-common [5] https://build.opensuse.org/package/show/home:darix:ruby/ruby2.2 [6] https://github.com/openSUSE/gem2rpm/commits/master

4 18

Two stage Ruby compilation / Bootstrapping
by Vít Ondruch 19 Nov '20

19 Nov '20

Hi all, Ruby upstream is implementing more and more stuff directly in Ruby. We already had issues, that build of Ruby required Ruby when we did some modifications [1]. In subsequent ticket, one of Ruby committers said [2]: > ... snip ... > BASERUBY is already a build requirement > ... snip ... > I would like to implement more of Ruby using Ruby, so miniruby may depend on prelude one day. With recent changes, such as [3], I am afraid that the day has come. Previously, if you wanted to patch lets say "gem_prelude.rb", it was enough to patch it. But now you *need* Ruby to process it into miniprelude.c. There are possibly 4 ways out of this. 1) Build Ruby in two stages. a) build (mini)ruby, apply patches b) build Ruby using the previously built (mini)ruby. 2) Use previous version of Ruby available in Fedora to bootstrap Ruby. But this does not work ATM, at least when RubyGems are installed. And upstream is doing what they can to make RubyGems inseparable [4]. 3) Prepare patches locally and apply the required changes also to the pregenerated files. But the problem here is, that the patches might unpredictably fail between updates. I don't think that they keep any API/ABI promises for the tools used to generate those files. 4) Don't use the upstream tarball, but generate it from sources with patches integrated. I think we should probably start to take look at 1), specifically into the *miniruby* variant if that is enough. If that is done, the 2) could optionally blend in. And in the mean time use 3) because otherwise I really don't know how to integrate the ABRT hook support. I don't like 4) at all, unless we have some Fedora standardized way of doing so. On the positive side, 1(2) would allow us to stay better in line with "Pregenerated code" guidelines [5], because there is already quite a lot of pre-generated code shipped in Ruby release tarball. Thoughts? Vít [1] https://src.fedoraproject.org/rpms/ruby/c/c0513dfb8c81a228619c6142195c5117a… [2] https://bugs.ruby-lang.org/issues/15306#note-1 [3] https://github.com/ruby/ruby/pull/2655 [4] https://bugs.ruby-lang.org/issues/16431 [5] https://docs.fedoraproject.org/en-US/packaging-guidelines/what-can-be-packa…

3 7

Retired "rubygems" package
by Vít Ondruch 15 May '20

15 May '20

Hi all, The independent "rubygems" package was retired, because it FTBFS already for some while: https://src.fedoraproject.org/rpms/rubygems/c/366607586d95b505277165fce54d9… Now I wonder, do we care? Should I unretire it while there is a chance to do it without review or we don't care and we are fine with the bundled version shipped in Ruby? Obviously if I was convinced we really need it, I'd did that without asking. So what are your opinions? Vít

3 3

Ruby 2.7
by Vít Ondruch 16 Jan '20

16 Jan '20

Hi everybody, I have create PR with .spec file, which will eventually become Ruby 2.7 package in Fedora some time around beginning of next year: https://src.fedoraproject.org/rpms/ruby/pull-request/48 and this is associated scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=36285060 I was considering, if I should open PR from my fork or push everything into the main repository, but I have decided to push directly into private-ruby-2.7 branch, so all the changes are preserved. Now what has changed? * Upstream move to Git, so I have updated the .spec file to use git hashes instead of SVN releases. No upgrade path is guaranteed. * The bundled gems now ships with RubyGems stubs, that means there should not be conflicts between for example /usr/bin/rake shipped by ruby and rubygem-rake. That should make it easier to install these packages side by side (and help for example with Bundler 2.x transition). * The bundler Racc now ships with its executable, therefore I have decided to move it into rubygem-racc subpackage. * I have removed support for %{rubygems_default_filter} macro. Nobody (except rubygem-rugged) ever used this macro and it never provided any real functionality (rhbz#1020810). And that is it. I'll keep updating the branch as I find time. As always, I welcome any feedback here or in the PR. Vít

3 16

Ruby 2.7 change proposal
by Vít Ondruch 13 Dec '19

13 Dec '19

Hi Rubyists, The release of Ruby 2.7 is coming close and to be ready for rebuild after Christmas, I have submitted the Ruby 2.7 change proposal [1]. It is already in `ChangeReadyForWrangler` state, since I don't expect any controversy. But anyway, please review and let me know if you have any concerns. Vít [1] https://fedoraproject.org/wiki/Changes/Ruby_2.7

1 0

Rspec 3.9.0
by Pavel Valena 10 Dec '19

10 Dec '19

Currently, I've experimentally built Rspec 3.9, and I'm trying to enable tests, and I'm getting: -- Pavel Valena Software Engineer, Red Hat Brno, Czech Republic

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

ruby-sig December 2019