Hello Nils (and the ruby team in cc),

Am Sat, Jun 15, 2024 at 08:39:54AM +0200 schrieb Nils Landt:
> > 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.

it has been a very long time that I kept your message in my inbox, but
I finally got back to it - cheers to email based workflows!

I have just submitted a patch to remove ruby@2.6:
   https://issues.guix.gnu.org/77289

Unfortunately it seems to entail a rebuild of ruby@2.7 (and its
thousands of dependencies); an unintended consequence of removing
inheritance, or a mistake in my copy-pasting of field values?

ruby@3.0 could also be dropped, and ruby@3.2 has only one dependent
package, which maybe could be made to depend on ruby@3.3 instead.

Moving the dependents of ruby@2.7 to depend on ruby@3 instead would be
nice, but maybe is a Herculean work.

Andreas


Reply via email to