[Bug 258108] devel/ruby-gems: Update to 3.2.26 (Fixes for Ruby 3.0)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258108

Thibault Jouan <tj+freebsd_ports@a13.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tj+freebsd_ports@a13.fr

--- Comment #9 from Thibault Jouan <tj+freebsd_ports@a13.fr> ---
Created attachment 228666
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=228666&action=edit
update to 3.2.29

Hello,

  I hope I'm not overstepping, but I'm currently looking into RubyGems
3.2 update too. I tried with version 3.2.29, with the original
approach of removing bundler, but with as few manual changes as I
could (since as noted, we cannot rely on `USE_BUNDLER_FOR_GEMDEPS'
anymore).

  My detailed notes are in the patch, at the top. I usually test
patches (such as this one) for weeks/months before submitting or
publishing, but given that current RubyGems port is old, and that Ruby
3.1 will be out soon, I hoped that sharing this work could help.

  I have only tested a few dozens gems (half written by me), with
`lang/ruby27' and `lang/ruby30' for now, but will continue testing
over the next days. The most annoying issue from my point of view, is
the new `%%GEMS_BASE_DIR%%/plugins' directory created when installing
gem via the port system (during FreeBSD package build), I don't know
how to handle this (gems ported with RubyGems 3.0.8 will generate a
different package once `devel/ruby-gems' is updated to 3.2.29).

-- 
You are receiving this mail because:
You are the assignee for the bug.