Date: Fri, 27 Aug 2021 23:38:47 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: maintainer-feedback requested: [Bug 258108] devel/ruby-gems: Update to 3.2.26 (Fixes for Ruby 3.0) Message-ID: <bug-258108-21402-5OlJdBKgX0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-258108-21402@https.bugs.freebsd.org/bugzilla/> References: <bug-258108-21402@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Bugzilla Automation <bugzilla@FreeBSD.org> has asked freebsd-ruby (Nobody) <ruby@FreeBSD.org> for maintainer-feedback: Bug 258108: devel/ruby-gems: Update to 3.2.26 (Fixes for Ruby 3.0) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D258108 --- Description --- The attached patch updates devel/ruby-gems to 3.2.26 (Latest available as of 2021-08-27). This obviates 256080 (the port will no longer be broken). I'm running gem installed from this port at work with Ruby 3.0, and on my personal box with Ruby 3.7 - seems to be working. Needs QA - in particular: The staging installed under /usr/local/bin/gem instead of /usr/local/bin/gem/${RUBY_VER_SHORT} I hacked the Makefile to move and symlink it so it behaves "properly" (the = way it previously did) but I feel like I'm missing something stupidly obvious that's causing it to misbehave in the first place. The 3.2.26 install includes Bundler and bunch of Bundler-related "stuff" - I ripped that out of the packing list since we have sysutils/rubygem-bundler = for this. It doesn't appear to break anything with gem's functionality and sysutils/rubygem-bundler installs cleanly with this updated port so I think= my packing list is clean, but please sanity check me here.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-258108-21402-5OlJdBKgX0>