Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 Oct 2021 08:10:14 +0000
From:      bugzilla-noreply@freebsd.org
To:        ruby@FreeBSD.org
Subject:   [Bug 259491] devel/ruby-gems: it should be updated to 3.1.x
Message-ID:  <bug-259491-21402-J0q72HM9Qc@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

--- Comment #4 from deivid.rodriguez@riseup.net ---
I wanted to keep writing but I liked submit too early :sweat_smile:

Wen Heping, yes, 3.1.5 would be better, I forgot that we had released one m=
ore
patch level 3.1 version hehe.

Thibault Jouan, thanks so much for the context and for your work. If the
upgrade to 3.1 is too hard, and there's already work going on to upgrade to
3.2, then 3.2 is also perfectly fine. While we don't test or consider the
scenario of using a rubygems version older than the one shipped with each
upstream ruby, we _do_ test the latest rubygems version against all rubies =
we
support, so that should work just fine. And it's also a much better version
that 3.1 :)

3.1 is not actively maintained, we have only backported a few fixes so that
they can be shipped with further 2.7.x patch level versions of ruby. But
nothing other than that.

It sounds like https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D258108 is
quite close to being ready? That would be pretty awesome!

--=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-J0q72HM9Qc>