| 1 |
On Sun, 2016-12-04 at 09:40 +0100, Matthias Hanft wrote: |
| 2 |
> Hans de Graaff wrote: |
| 3 |
> > |
| 4 |
> > |
| 5 |
> > Ruby MRI 2.0 has been retired by upstream in February 2016.[1] |
| 6 |
> > We remove Ruby MRI 2.0 support from the tree now. Ruby MRI 2.1 |
| 7 |
> > remains |
| 8 |
> > activated in base profile's RUBY_TARGETS variable by default. |
| 9 |
> |
| 10 |
> Hmmm... what about dependencies? |
| 11 |
> |
| 12 |
> Are they obsolete, too? Should I just "emerge -C =ruby-2.0.0_p648"? |
| 13 |
> Or is there some kind of "ruby-cleaner" (like "perl-cleaner") to |
| 14 |
> switch all that to ruby 2.1? How to proceed in order to get a |
| 15 |
> consistent 2.1 installation? As a normal user, I'd get stuck at |
| 16 |
> this point without further instructions... |
| 17 |
|
| 18 |
Most dependencies are not obsolete, although installing them with the |
| 19 |
ruby20 target is. We don't have a ruby-cleaner tool, but re-installing |
| 20 |
packages with the -N flag of emerge should work. After doing that |
| 21 |
ruby:2.0 can be depcleaned. I've added this to the news item: |
| 22 |
|
| 23 |
---- |
| 24 |
Packages can be reinstalled for ruby21 only by using the -N option of |
| 25 |
emerge: |
| 26 |
|
| 27 |
emerge -uvDNq world |
| 28 |
---- |
| 29 |
|
| 30 |
Hans |
Archives