Date: Wed, 29 Dec 2021 05:01:50 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: maintainer-feedback requested: [Bug 260780] devel/ruby-gems: Sending a patch for updating to 3.3.3 Message-ID: <bug-260780-21402-5YJooLcQRi@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260780-21402@https.bugs.freebsd.org/bugzilla/> References: <bug-260780-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 260780: devel/ruby-gems: Sending a patch for updating to 3.3.3 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260780 --- Description --- This diff provides an update to the latest version 3.3.3 for devel/ruby-gems As well as the version update, the patch introduces a new behavior to the p= ort build in that it will not produce the bin/gem symlink unless the build is b= eing produced under the default ruby version. afaict this may help to prevent so= me pathname collisions under builds for different Ruby versions. I'd added th= is with the update, after how the symbolic linking is approached e.g in lang/ruby30=20 Outside of the particular idea for the symlink handling under the 'gem' cmd, this update may help to resolve some issues for resolving gemspec pathnames under bin or exec files for gems, e.g the 'irb' command I've tested this patch under Ruby 3.0 HTH - Sean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260780-21402-5YJooLcQRi>