This is a very annoying and somewhat stupid bug. I have both ruby 1.9 and 1.8 installed. 1.9 is set as my default ruby profile. Some apps only support 1.8, and in these cases there seems to be issues in configuring the ruby portion correctly. All of these fail for me one way or another, and the solution for all of this is to export the environment variable RUBYOPT="" when emerging these packages. Haven't really dug into this to see why this is an issue since I knew a way around it, but since this has become an issue with subversion recently as well, I figured a bug needed to be filed. Reproducible: Always
Please file a single bug for every single package so that bugs can be assigned properly to their respective maintainers instead of being piled up in a big heap that no one wants to touch. Make those new bug block[1] this bug. (Of course perhaps this tracker isn't needed at all, but I'll leave that up to ruby@g.o people to decide.) [1] https://bugs.gentoo.org/page.cgi?id=fields.html#blocked
No prob. Done.
(In reply to comment #1) > (Of course perhaps this tracker isn't needed at all, but I'll leave that up > to ruby@g.o people to decide.) Ruby 1.8 will go away in the summer of 2013 when upstream stops security support for it, so we need to fix this bugs before that time (and hopefully much sooner). Current expectation is that we'll make ruby 1.9 the default ruby provider sometime this fall.
Wanted to add a note here that I found part of what was causing some problems with subversion's ruby support. Here's a copy/paste from that bug: --snip-- I have the ruby USE flag globally enabled (I do a lot of ruby related work) but I'm trying to use ruby 1.9 over 1.8 when possible. So I have RUBY_TARGETS="ruby19". ruby 1.8 still get pulled in though, by a few packages that do not yet support 1.9. However, since I only have RUBY_TARGETS="ruby19", rubygems does not get built for 1.8, which is what is causing this problem. After adding "dev-ruby/rubygems ruby_targets_ruby18" to /etc/portage/package.use and re-emerging rubygems, subversion emerges correctly. --snip-- Don't know if this has much to do with the other bugs, but I thought it might be of interest.
Aha, in that case ruby19 provides the RUBYOPT stuff (to be compatible with ruby18, oh irony), and then ruby18 fails because it's actually rubygems that installs the extra code. I guess we could solve this with PDEPEND on rubygems in the dev-lang/ruby:1.8 builds. Alex, Diego: a I missing something here, or should be just add this?
We now have a security bug for ruby 1.8 that will not get fixed upstream. Let's push for masking of ruby 1.8 either this weekend or the next.
19 Apr 2014; Manuel Rüger <mrueg@gentoo.org> -ruby-1.8.7_p374-r1.ebuild, -ruby-1.8.7_p374.ebuild: Remove Ruby 1.8. See bug #434064.
