From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SX7X9-0004oe-0K for garchives@archives.gentoo.org; Wed, 23 May 2012 09:07:07 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8DE6CE07F8 for ; Wed, 23 May 2012 09:07:06 +0000 (UTC) Received: from iguard11-13.hkbn.net (iguard11-13.hkbn.net [210.6.3.13]) by pigeon.gentoo.org (Postfix) with ESMTP id 43397E066E for ; Wed, 23 May 2012 08:00:23 +0000 (UTC) Received: from outguard01.hkbn.net ([203.186.94.187]) by iguard11.hkbn.net with ESMTP; 23 May 2012 16:00:21 +0800 Received: from outguard01.hkbn.net (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 18B1E3D003C for ; Wed, 23 May 2012 16:00:21 +0800 (HKT) Received: from smtpo.ctimail.com (unknown [203.186.94.58]) by outguard01.hkbn.net (Postfix) with ESMTP id 7EB273D003D for ; Wed, 23 May 2012 16:00:20 +0800 (HKT) Received: from gentoo-main.kwkh-home (183178212219.ctinets.com [183.178.212.219]) by smtpo.ctimail.com (8.14.5/8.14.5) with ESMTP id q4N80Irg010417 for ; Wed, 23 May 2012 16:00:20 +0800 Date: Wed, 23 May 2012 15:58:46 +0800 From: kwkhui@hkbn.net To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Understanding new ruby dependencies Message-ID: <20120523155846.7c28c059@gentoo-main.kwkh-home> In-Reply-To: References: <62nr89-2v2.ln1@graaff.xs4all.nl> <20120523023252.57927f37@gentoo-main.kwkh-home> <4FBC5670.6070705@orlitzky.com> <20120523131327.10eeeebe@gentoo-main.kwkh-home> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA512; boundary="Sig_/ZitzqtMJZsR8Rn=R9k133RV"; protocol="application/pgp-signature" X-TM-AS-Product-Ver: IMSVA-8.2.0.1391-6.8.0.1017-18922.005 X-TM-AS-Result: No--22.711-9.9-31-10 X-imss-scan-details: No--22.711-9.9-31-10;No--22.711-5.0-31-10 X-TMASE-Version: IMSVA-8.2.0.1391-6.8.1017-18922.005 X-TMASE-Result: 10--22.710800-5.000000 X-TMASE-MatchedRID: dL10VBB8yocOwH4pD14DsPHkpkyUphL9LC92/N1OWlme9toQ6h6LEzdT XiRLG6kOf1o8m5wQHNlk73ryAgupfTpI0A0aNTmU7g3VxUiA33uHxi2fvkKUM78UoF+40jlL1BJ Bp0wn7V9RZs8P2Evgu80QG0q31+izJkdUoMFZ1eVIRA38P/dwbgRryDXHx6oXemIOfEwRhx0sX2 NvG8rX7fx1ilfYH0RSSgzHO8ZZA29pYWjXb2NmkAPZZctd3P4BHznaOB9+eYg7QfbJ2yvx5dEw+ lHrZKHl4Ieo9EbPx6Pj+YJP7vuP7DQz4qxNxMYHsyw+ZJnFumS/yN2q8U674pCuKABMXnFn75T4 BPuNkdpmHUDR4UU49DM7njxfVliJS2vb/Rh+9IXDDmXNk+rLpRbjReJSRusbfeHPnu31iHDjElR IM3bmKC/layKw2sQTXMCLraxngrl16NuLD9SbQo9URkDgdlb5I5K4Cd+0ao8Y0A95tjAn+x+DSw DUdPbGDYUI0IWXQA+zLCnUz3MHY/LKLUxaI15jw69AIwXJn0YhauGyjTkf9X6fP1funxvCrcmmD 7/hK1+k8oKXKhRLPKk+N2rAH2pF5tHwb6x0QAglCGssfkpInQ== X-Archives-Salt: fd911acb-7705-43ef-a016-71f677ab65ff X-Archives-Hash: 4554b8c1921ae87edc7f836fe2478452 --Sig_/ZitzqtMJZsR8Rn=R9k133RV Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 22 May 2012 23:35:21 -0700 Chris Stankevitz wrote: > On Tue, May 22, 2012 at 10:13 PM, 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. >=20 > Thank you for all your patient help. I've been using Gentoo for years > and for some reason this RUBY thing has me flustered. >=20 > 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=3D" rdoc? ( >=3Ddev-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=3D > /usr/portage/profiles/base/make.defaults:RUBY_TARGETS=3D"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 cons= idered "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=3D"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=3Druby19 would have expanded to) enabled and so that is what portage did (and screamed when it can't). Kerwin. --Sig_/ZitzqtMJZsR8Rn=R9k133RV Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBCgAGBQJPvJi3AAoJEN8jXmjJyWMkmJsP/3qsTYjv/ib510oVfpUO6re5 +mcMIeCLRSONNiCH3v3Attva5LBRZv4FAneojY9Dxtkx3oZfEISFiu1eqtBO6Mjh 5LVbxvscmwayPhNMsst66YuhLQlxNeGTgDXfSzgk0zCoFBw9I4/e2iesPbD4VEJP JUHh/3QryeCiKGcW7Y5IXPb7BFj+4LqdB0wAPYdzAADYg2LHn1EncD+98UaQTlZU Jm3JXsS5kErX/lXQqzthvw2GSGN/eQ/9kFjo/zkCLtYQ2WCYlpD1oxOx7JRIlwQT 7bd+aiKfKbzMbjuq4mOqGWfhO7MoWQa8vOd2hmnpH5Wytr24oLvoF6y5cG5wrSjP ypCQfAqkvQbR5OBIH70CkY6B8HckDDU7d+a9vmebc9NmDQT/3l/HOcO/Ppjdapts 4DOZzb4crL5Y8KrkqIH55PVIcFZQzo1SoMDW2wkrP2AlXSmo/pTe6gu45lzjWzQg XSS7C3lk23KYyDNX1VQXnPIGkJS1VfmOH0cWwfhLWWR+VJHzfsSm43j1HYkKUkc4 QE2Lh4DfPUncfHkpr6sC3MR9Um8vUHp+3NxTnF6FlAxslfwsM0Z0baODH+YuiMfy O0F7S8mjKp2wo/G5ZQtvDbKuNO8an3ytoL5KTvDfObNcBnIs3B3Jo+dcz5OJgz6v HCvbConW6fKS4LJXOKiB =IWP1 -----END PGP SIGNATURE----- --Sig_/ZitzqtMJZsR8Rn=R9k133RV--