On Sun, 2016-12-04 at 09:40 +0100, Matthias Hanft wrote: > Hans de Graaff wrote: > > > > > > Ruby MRI 2.0 has been retired by upstream in February 2016.[1] > > We remove Ruby MRI 2.0 support from the tree now. Ruby MRI 2.1 > > remains > > activated in base profile's RUBY_TARGETS variable by default. > > Hmmm... what about dependencies? > > Are they obsolete, too? Should I just "emerge -C =ruby-2.0.0_p648"? > Or is there some kind of "ruby-cleaner" (like "perl-cleaner") to > switch all that to ruby 2.1? How to proceed in order to get a > consistent 2.1 installation? As a normal user, I'd get stuck at > this point without further instructions...
Most dependencies are not obsolete, although installing them with the ruby20 target is. We don't have a ruby-cleaner tool, but re-installing packages with the -N flag of emerge should work. After doing that ruby:2.0 can be depcleaned. I've added this to the news item: ---- Packages can be reinstalled for ruby21 only by using the -N option of emerge: emerge -uvDNq world ---- Hans
signature.asc
Description: This is a digitally signed message part
