| 1 |
On Tue, 22 May 2012 23:35:21 -0700, Chris Stankevitz wrote: |
| 2 |
|
| 3 |
> 1. What on my system is insisting on make.conf RUBY 1.9 USE_EXPAND |
| 4 |
> changes? An emerge --tree is not giving me a clear answer (as it |
| 5 |
> usually does). The original post in this thread provides a pastebin |
| 6 |
> link to back up this claim. |
| 7 |
|
| 8 |
It is implicit. dev-lang/ruby:1.9 requires a new enough version of rdoc |
| 9 |
with this particular USE flag enabled. |
| 10 |
|
| 11 |
> 2. If the answer to (1) is "the gentoo system itself", then why doesn't |
| 12 |
> "the gentoo system itself" update the USE_EXPAND by adding a reference |
| 13 |
> to ruby19? It appears "the gentoo system itself" presently only enables |
| 14 |
> the ruby18 USE_EXPAND. |
| 15 |
> base $ find /usr/portage/profiles/ | xargs grep RUBY_TARGETS= |
| 16 |
> /usr/portage/profiles/base/make.defaults:RUBY_TARGETS="ruby18" |
| 17 |
|
| 18 |
Right. We'll add ruby19 to that shortly. The reason we did not do that |
| 19 |
before was that we wanted to ease into ruby19, but there seem to be |
| 20 |
plenty of people that have a package depending on dev-lang/ruby on their |
| 21 |
system, so that plan didn't work very well. |
| 22 |
|
| 23 |
> 4. I run a "stable" system that is somehow insisting on ruby19. This |
| 24 |
> webpage http://www.gentoo.org/proj/en/prog_lang/ruby/index.xml says |
| 25 |
> ruby19 is not for use on production systems. Why the disconnect? |
| 26 |
> Perhaps the ruby page is just out of date. |
| 27 |
|
| 28 |
Correct conclusion, and I've just updated it for the various ruby |
| 29 |
implementations. |
| 30 |
|
| 31 |
> Thank you for listening to me list the issues I am ignorant on. Now I'm |
| 32 |
> going to add RUBY_TARGETS="ruby19" to my make.conf and hope things "just |
| 33 |
> work". |
| 34 |
|
| 35 |
At this point I would recommend RUBY_TARGETS="ruby18 ruby19". |
| 36 |
|
| 37 |
Kind regards, |
| 38 |
|
| 39 |
Hans |
Archives