Created attachment 354214 [details, diff] rdoc-4.0.1-r1.ebuild.patch if i only enable ruby20 target i'll get broken dep tree like this The following USE changes are necessary to proceed: (see "package.use" in the portage(5) man page for more details) # required by dev-ruby/json-1.8.0[-doc,-test,ruby_targets_ruby19] # required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby20] # required by dev-lang/ruby-1.9.3_p448[rdoc] # required by virtual/rubygems-4 # required by dev-ruby/racc-1.4.9[-test,ruby_targets_ruby19] >=dev-ruby/rake-0.9.6 ruby_targets_ruby19 # required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby19] # required by dev-lang/ruby-1.9.3_p448[rdoc] # required by virtual/rubygems-4 # required by dev-ruby/json-1.8.0[-test,ruby_targets_ruby19] # required by dev-lang/ruby-2.0.0_p247 # required by dev-ruby/rubygems-2.0.3[ruby_targets_ruby19] # required by virtual/rubygems-6 # required by dev-ruby/rake-0.9.6 >=dev-ruby/racc-1.4.9 ruby_targets_ruby19 # required by dev-lang/ruby-1.9.3_p448[rdoc] # required by virtual/rubygems-4 # required by dev-ruby/racc-1.4.9[-test,ruby_targets_ruby19] >=dev-ruby/rdoc-4.0.1-r1 ruby_targets_ruby19 # required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby19] # required by dev-lang/ruby-1.9.3_p448[rdoc] # required by virtual/rubygems-4 # required by dev-ruby/racc-1.4.9[-test,ruby_targets_ruby19] >=dev-ruby/json-1.8.0 ruby_targets_ruby19 # required by dev-lang/ruby-1.9.3_p448 # required by virtual/rubygems-4 # required by dev-ruby/racc-1.4.9[-test,ruby_targets_ruby19] # required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby19] # required by dev-lang/ruby-2.0.0_p247[rdoc] # required by dev-ruby/rake-0.9.6[ruby_targets_ruby20] # required by dev-ruby/json-1.8.0[-doc,-test,ruby_targets_ruby19] >=dev-ruby/rubygems-2.0.3 ruby_targets_ruby19
Created attachment 354216 [details, diff] rubygems-2.0.3.ebuild.patch
These patches should not be needed since each ebuild already depends on ruby:2.0. The dependencies for the other ruby targets are there only because we want specific versions of each ruby interpreter. That is not the case for ruby20. From your bug description it is not clear to me what the problem is. The portage output you have included does not show the actual problem. Also note that using ruby20-only is currently not a practical thing to do since only very few packages are currently marked for ruby20.
*** Bug 483596 has been marked as a duplicate of this bug. ***
Note that the problem originally reported is now fixed by requiring ruby20 for these packages.