So, currently RUBY_TARGETS="ruby25 ruby26" on amd64. IIRC, portage handles || deps by going with the first. For the current subversion ebuild, above means RUBY_DEPS evaluates to ruby:2.6 regardless of RUBY_TARGETS value. So, setting RUBY_TARGETS to just 'ruby25' has no effect on dependency calculation. (I will likely upgrade to 2.6 soon, but not quite now) Perhaps, given that portage implementation detail, it would be better if ruby-single eclass added ruby versions in reverse slot order ?
The relevant part of DEPEND in dev-vcs/subversion-1.14.0-r1 currently evaluates to this: ruby? ( || ( dev-lang/ruby:2.5 dev-lang/ruby:2.6 ) ) I assume pulls in dev-lang/ruby:2.6 because it is the highest visible version. See bug 705700 comment 12.
(In reply to Mike Gilbert from comment #1) ...well, ok, this does look like it's pretty much a dupe of bug 702806 then. *** This bug has been marked as a duplicate of bug 702806 ***
The ruby-utils eclass was not updated yet to prefer ruby26 as the best target. This has now been fixed and should address this issue.
(In reply to Hans de Graaff from comment #3) > The ruby-utils eclass was not updated yet to prefer ruby26 as the best > target. This has now been fixed and should address this issue. ...given what I've wrote opening this bug, it should have been obvious I see that as an opposite of a fix. I did read at least a part of the bug I marked this one as a dupe of.
