Currently this pulls in ruby20 because it depends on dev-lang/ruby directly. Either we should drop the useflag or add some ruby-eclass stuff to it, so it depends on a sane slot based on RUBY_TARGETS. Another possibility is masking the ruby useflags.
[nomerge ] app-text/docbook-xsl-stylesheets-1.78.0 USE="ruby" [nomerge ] dev-lang/ruby-2.0.0_p247-r1:2.0 [1.8.7_p374:1.8, 1.9.3_p448:1.9] USE="berkdb gdbm ipv6 ncurses rdoc readline ssl tk yaml -debug -doc -examples -rubytests -socks5 -xemacs" [ebuild R ] dev-ruby/rdoc-4.0.1-r1 USE="-doc {-test}" RUBY_TARGETS="ruby18 ruby19 ruby20* -jruby" 0 kB [ebuild R ] dev-ruby/racc-1.4.9 USE="-doc {-test}" RUBY_TARGETS="ruby18 ruby19 ruby20* -jruby" 0 kB [ebuild U ] dev-ruby/json-1.8.0 [1.7.7] USE="-doc {-test}" RUBY_TARGETS="ruby18 ruby19 ruby20%* -jruby (-ree18%)" 146 kB [ebuild R ] dev-ruby/rake-0.9.6 USE="-doc {-test}" RUBY_TARGETS="ruby18 ruby19 ruby20* -jruby" 0 kB [ebuild NS ] virtual/rubygems-6:ruby20 [1:ruby18, 4:ruby19] RUBY_TARGETS="(ruby20)" 0 kB [ebuild R ] dev-ruby/rubygems-2.0.3 USE="-server {-test}" RUBY_TARGETS="ruby18 ruby19 ruby20* -jruby" 0 kB [ebuild NS ] dev-lang/ruby-2.0.0_p247-r1:2.0 [1.8.7_p374:1.8, 1.9.3_p448:1.9] USE="berkdb gdbm ipv6 ncurses rdoc readline ssl tk yaml -debug -doc -examples -rubytests -socks5 -xemacs" 10,554 kB Deptree. Or we could add a virtual/any-ruby which is satisfied by || ( any-existing-ruby-interpreter ) and make it depend on this.
Created attachment 359582 [details, diff] docbook-xsl-stylesheets-1.78.0.ebuild.patch I'm not sure if this will work or not?
(In reply to Manuel Rüger from comment #1) > Or we could add a virtual/any-ruby which is satisfied by || ( > any-existing-ruby-interpreter ) and make it depend on this. Can't do that since we can't guarantee compatibility between versions. Each package needs to express its compatibility in some way.
(In reply to Manuel Rüger from comment #2) > Created attachment 359582 [details, diff] [details, diff] > docbook-xsl-stylesheets-1.78.0.ebuild.patch > > I'm not sure if this will work or not? I think we should create a simple eclass that, for now, just manages the ruby dependencies based on USE_RUBY and RUBY_OPTIONAL. We can extend it later with proper support for compiling bindings. app-text/xmlformat is another candidate for this. Right now I've solved this same problem there by depending on || ( ruby:1.9 ruby:2.0 ).
(In reply to Hans de Graaff from comment #4) > Right now I've solved this > same problem there by depending on || ( ruby:1.9 ruby:2.0 ). Thanks, I added a -r1 with the same fix. Yeah the eclass approach will be of course the better way to solve this.