On 12/11/2013 02:47 AM, Hans de Graaff wrote: > >> During a transition period like this, various upstreams release a bunch >> of crap with circular or conflicting dependencies that happen to work on >> their machines because nobody is using a real package manager. The fact >> that it works as well as it does is a miracle. If you don't want all >> three versions of Ruby on your machine, try setting e.g. >> RUBY_TARGETS="ruby19". It probably won't work, but that's because some >> package has troublesome dependencies, not because we're handling it >> wrong. > > It should work (I have some machines with that setting). Two things to > keep in mind: you are now off the default settings, so you will need to > manage new ruby targets yourself. You will also still get the ruby20 core > installed for the moment due to weird dependency issues with some > packages. This will get rectified when we add ruby20 to the default > RUBY_TARGETS.
If anything needs ruby, you get whatever version of ruby it wants (say, 1.9). But then the next time you emerge -puDN world, you pull in dev-lang/ruby-2.0 in a different slot. But ruby-2.0 needs rdoc, rake, and json with USE=ruby_targets_ruby20. Down the rabbit hole we go =) I did finally get RUBY_TARGETS="ruby19" working but I had to package.mask ruby-2.0 first.
