Re: [gentoo-user] Re: Understanding new ruby dependencies

[Chris Stankevitz]

On Tue, May 22, 2012 at 10:13 PM,  <kwkhui@××××.net> wrote:
> I suggest keeping an eye on ${PORTDIR}/profiles/desc directory too.
> This is where every one of the USE_EXPAND variables is explained in
> details.

Thank you for all your patient help.  I've been using Gentoo for years
and for some reason this RUBY thing has me flustered.

1. What on my system is insisting on make.conf RUBY 1.9 USE_EXPAND
changes?  An emerge --tree is not giving me a clear answer (as it
usually does).  The original post in this thread provides a pastebin
link to back up this claim.

2. If the answer to (1) is "the gentoo system itself", then why
doesn't "the gentoo system itself" update the USE_EXPAND by adding a
reference to ruby19?  It appears "the gentoo system itself" presently
only enables the ruby18 USE_EXPAND.
  base $ find /usr/portage/profiles/ | xargs grep RUBY_TARGETS=
  /usr/portage/profiles/base/make.defaults:RUBY_TARGETS="ruby18"

3. If the answer to (1) is "package foo", I'm tempted to remove
package foo or USE it with -ruby or "eat my words" and admit that I am
a RUBY user and need to understand the nuances.

4. I run a "stable" system that is somehow insisting on ruby19.  This
webpage http://www.gentoo.org/proj/en/prog_lang/ruby/index.xml  says
ruby19 is not for use on production systems.  Why the disconnect?
Perhaps the ruby page is just out of date.

5. I have no idea what RUBY is and have never installed it directly.
Yet I have to understand RUBY USE_EXPANDs which seem to be described
only in the RUBY installation guide, gentoo dev manual, or in ebuild
scripting guides.  I am a gentoo "layperson" in general and am
completely clueless about RUBY in particular.  I believe talk about
this "required and automatically installed package" should appear not
in obscure dev documentation, but in the handbook.  Perhaps with more
time/volunteers this would have happened.

6. Why does emerge insist on me adding USE="ruby_targets_ruby19" to a
bunch of projects, yet the users of this group recommend a change in
make.conf?  I suspect the disconnect that the two approaches are
equivalent, just emerge does not have the "street smarts" to recommend
the proper change.

Thank you for listening to me list the issues I am ignorant on.  Now
I'm going to add RUBY_TARGETS="ruby19" to my make.conf and hope things
"just work".

Thank you again,

Chris