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?
home01 ~ # eshowkw ruby
Keywords for dev-lang/ruby:
| | u |
| a a a n p r s | n |
| l m r h i m m i p i s p | u s | r
| p d a m p a 6 i o p c s 3 a x | s l | e
| h 6 r 6 p 6 8 p s p 6 c 9 s r 8 | e o | p
| a 4 m 4 a 4 k s 2 c 4 v 0 h c 6 | d t | o
--------------+---------------------------------+-------+-------
[I]2.0.0_p648 | + + + o + + o ~ o + + o ~ ~ + + | o 2.0 | gentoo
--------------+---------------------------------+-------+-------
[I]2.1.9 | + + + o + + o ~ o + + o ~ ~ + + | o 2.1 | gentoo
home01 ~ # eselect ruby list
Available Ruby profiles:
[1] ruby20 (with Rubygems)
[2] ruby21 (with Rubygems) *
home01 ~ # emerge -pvc =ruby-2.0.0_p648
Calculating dependencies... done!
dev-lang/ruby-2.0.0_p648 pulled in by:
dev-ruby/json-1.8.2-r1 requires dev-lang/ruby:2.0
dev-ruby/racc-1.4.11 requires dev-lang/ruby:2.0
dev-ruby/rake-10.5.0 requires dev-lang/ruby:2.0
dev-ruby/rdoc-4.2.0 requires dev-lang/ruby:2.0
dev-ruby/rubygems-2.5.2 requires dev-lang/ruby:2.0
virtual/rubygems-10 requires dev-lang/ruby:2.0
>>> No packages selected for removal by depclean
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...
-Matt
