Date: Fri, 20 Feb 2026 17:48:22 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: maintainer-feedback requested: [Bug 293316] lang/ruby40: Ruby32, and Ruby40 are incomplete Message-ID: <bug-293316-21402-rqIoUEK8aQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-293316-21402@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
Bugzilla Automation <bugzilla@FreeBSD.org> has asked freebsd-ruby (Nobody) <ruby@FreeBSD.org> for maintainer-feedback: Bug 293316: lang/ruby40: Ruby32, and Ruby40 are incomplete https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293316 --- Description --- Hello I’m limited to using pkg(8) only. Building from the ports tree with RUBY_VER is not an option for me. On a standard Ruby installation, tools like gem, rake, and others are available out of the box. On FreeBSD though Ruby is split into multiple separate packages, and those separate packages are tied to a specific ruby version at build time through the RUBY_VER variable. That's problematic because neither the ruby32, nor the ruby40 port have any of those separate packages. They're left without a large part of their installation. And only ruby33 is complete (or can be complete, through additional packages). Am I misunderstanding how this is intended to work? Is there a recommended way to install and manage Ruby 3.2 or 4.0 with full tooling support using only pkg(8) ? I wish FreeBSD would just package standard Ruby instead of breaking it up into multiple ports, and creating problems like this in the process.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-293316-21402-rqIoUEK8aQ>