On Tue, 22 May 2012 23:35:21 -0700 Chris Stankevitz <chrisstankev...@gmail.com> wrote:
> On Tue, May 22, 2012 at 10:13 PM, <kwk...@hkbn.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.
Basically the newslot upgrade ruby 1.8.x -> 1.9.x.
For example, you can see that in
${PORTDIR}/dev-ruby/json/json-1.5.4-r1.ebuild there is the line
PDEPEND="
rdoc? ( >=dev-ruby/rdoc-3.9.4[ruby_targets_ruby19] )
xemacs? ( app-xemacs/ruby-modes )"
Previously in json-1.5.4.ebuild there is no such check, as you can
diff for yourself.
> 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"
That is usual... profile changes lag behind the ebuild changes.
> 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.
I suppose ruby19 is in a state similar to python3 --- not ready to be
default since *something* break, but it has been out long enough to be
considered "stable".
> 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.
TBH, I'm not a ruby person either. The only thing here on my system
that pulls in ruby is dev-texlive/texlive-pictures, plus I need ruby
for some random scripts I pulled from the web (which I could have
rewritten in python or bash but I can't be bothered).
> 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.
That is how ebuild (and hence portage) works --- it didn't check
RUBY_TARGETS but instead the specified use flags for dependencies
specified the ebuild. Hence the error message is "add use flag bar to
package foo, regardless of whether bar is actually an expanded flag. As
you see in the example above json ebuild tells portage to check
dev-ruby/rdoc is built with ruby_targets_ruby19 use flag (which is what
RUBY_TARGETS=ruby19 would have expanded to) enabled and so that is what
portage did (and screamed when it can't).
Kerwin.
signature.asc
Description: PGP signature
