Date: Fri, 29 Oct 2021 00:25:30 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 259491] devel/ruby-gems: it should be updated to 3.1.4 Message-ID: <bug-259491-21402-o0OmfD4ueX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-259491-21402@https.bugs.freebsd.org/bugzilla/> References: <bug-259491-21402@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259491 Thibault Jouan <tj+freebsd_ports@a13.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tj+freebsd_ports@a13.fr --- Comment #2 from Thibault Jouan <tj+freebsd_ports@a13.fr> --- hi, I think it has to do with Ruby 2.7.1 (port lang/ruby27), which printed keyword arguments warnings by default but it was fixed with Ruby 2.7.2 (#250050). If I'm correct, it happened even when using RubyGems (via `gem' command, not bundler calling RubyGems API). The current version of RubyGems is old indeed, some people have worked on the update since a while. From what I experienced and have seen (other PRs on the bug tracker, efforts on other RubyGems ports), the update to 3.1 is a little more involved than some past ones. There is of course the removal of `USE_BUNDLER_FOR_GEMDEPS', but also slightly more changes to the setup command than usual, the repository and history getting bigger, and there are the changes to the plugin system which aren't that big, but whatever solution we chose to adapt the port(s) there are many gems to check (ports of gems which depends on devel/ruby-gems). That may explain some delay. The most recent PR was #258108. However it targets RubyGems 3.2.30 (patches for 3.2.26, 3.2.29, and 3.2.30 attached), because it seemed that most difficulties were related to 3.0 -> 3.1, so once it's done, better use the last one than an old branch I think. Is 3.1 "actively" maintained and should we use that, or keep working on last 3.2? We have Ruby 2.6, 2.7, and 3.0 in ports (maybe 3.1 soon) so it has to work on all of them too. Note: I'm speaking from my point of view of RubyGems user and occasional patch writer or gem porter, not as someone making the actual changes and managing ports in FreeBSD. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-259491-21402-o0OmfD4ueX>