From: Nils Landt <nils@landt.email>
To: Andreas Enge <andreas@enge.fr>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Ruby without RVM - what to do if the version I want is missing?
Date: Sat, 15 Jun 2024 08:39:54 +0200 (CEST) [thread overview]
Message-ID: <1316652277.63955.1718433594861@office.mailbox.org> (raw)
In-Reply-To: <Zmx_hzZX0u9hWe1K@jurong>
> Andreas Enge <andreas@enge.fr> hat am 14.06.2024 19:36 CEST geschrieben:
>
> An interesting question would be whether all the packages that still depend
> on ruby@3.1 can use ruby@3.2 or ruby@3.3 instead.
There are breaking changes between these Ruby versions.
For most packages, upgrading Ruby and having the tests run would work, but I count 209 packages with tests disabled (I did not check how many of them run on 2.7).
Personally, I wouldn't want to risk it :)
> And whether we still need ruby@2.6 in addition to ruby@2.7; no package
> depends on the former.
Probably not, end of support for Ruby 2.6 was 2022-04-12.
Fwiw, end of support for 2.7 was 2023-03-30. The 2.7 -> 3.0 migration was pretty big in the Ruby ecosystem, I wouldn't expect there to be a lot of open source applications running 2.7 any more. Having a quick look at (gnu packagages ruby), very few packages still depend on 2.7.
next prev parent reply other threads:[~2024-06-15 6:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 15:43 Ruby without RVM - what to do if the version I want is missing? Daniel Littlewood
2024-06-14 16:15 ` Felix Lechner via
2024-06-14 17:36 ` Andreas Enge
2024-06-15 6:39 ` Nils Landt [this message]
2024-06-16 10:27 ` Andreas Enge
2024-06-17 19:09 ` Daniel Littlewood
2024-06-17 19:09 ` [bug#71559] " Daniel Littlewood
2024-06-19 15:50 ` Remco van 't Veer
2024-06-20 17:09 ` Andreas Enge
2024-06-15 7:43 ` Remco van 't Veer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1316652277.63955.1718433594861@office.mailbox.org \
--to=nils@landt.email \
--cc=andreas@enge.fr \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.