Date: Wed, 29 Dec 2021 05:01:50 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 260780] devel/ruby-gems: Sending a patch for updating to 3.3.3 Message-ID: <bug-260780-21402@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260780 Bug ID: 260780 Summary: devel/ruby-gems: Sending a patch for updating to 3.3.3 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ruby@FreeBSD.org Reporter: lab+bsd@thinkum.space Assignee: ruby@FreeBSD.org Flags: maintainer-feedback?(ruby@FreeBSD.org) Created attachment 230518 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=230518&action=edit Patch for devel/ruby-gems update to 3.3.3 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 port build in that it will not produce the bin/gem symlink unless the build is being produced under the default ruby version. afaict this may help to prevent some pathname collisions under builds for different Ruby versions. I'd added this with the update, after how the symbolic linking is approached e.g in lang/ruby30 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 -- 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-260780-21402>