Gentoo Archives: gentoo-user

From: kwkhui@××××.net
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: Understanding new ruby dependencies
Date: Wed, 23 May 2012 06:05:15
Message-Id: 20120523131327.10eeeebe@gentoo-main.kwkh-home
In Reply to: Re: [gentoo-user] Re: Understanding new ruby dependencies by Michael Orlitzky
1 On Tue, 22 May 2012 23:16:00 -0400
2 Michael Orlitzky <michael@××××××××.com> wrote:
3
4 > On 05/22/2012 09:10 PM, Chris Stankevitz wrote:
5 > >
6 > > How was I supposed to learn the "proper" way of dealing with this
7 > > RUBY-related system change?
8
9 That change was committed two-and-a-half years ago in the eclass:
10
11 http://archives.gentoo.org/gentoo-dev/msg_2305dbeaaf5b02cb74a84c9b06333708.xml
12
13 and the Gentoo Ruby project has a section on it
14
15 http://www.gentoo.org/proj/en/prog_lang/ruby/index.xml
16
17 Actually I learnt the RUBY_TARGETS from flameeyes's blog two years ago
18
19 http://blog.flameeyes.eu/2010/02/ruby-ng-package-in-a-bottle-or-learn-how-to-write-a-new-ruby-ebuild
20
21 > The way I learned was by watching the emerge output:
22 >
23 > $ emerge -pv dev-ruby/rails
24 >
25 > These are the packages that would be merged, in order:
26 >
27 > Calculating dependencies... done!
28 > [ebuild N ] app-admin/eselect-rails-0.16 2 kB
29 > [ebuild N ] dev-ruby/tmail-1.2.7.1-r2 USE="-debug -doc -test"
30 > RUBY_TARGETS="ruby18 -jruby -ree18" 436 kB
31 >
32 > and wondering, "RUBY_TARGETS, what the hell is that?"
33 >
34 > I'm sure there's a proper way, but that's the way I've discovered all
35 > of the USE_EXPAND variables. LINGUAS was the first, then I noticed
36 > ALSA_CARDS, APACHE2_MODULES, XFCE_PLUGINS...
37 >
38 > The default list can be found in,
39 >
40 > /usr/portage/profiles/base/make.defaults
41
42 I suggest keeping an eye on ${PORTDIR}/profiles/desc directory too.
43 This is where every one of the USE_EXPAND variables is explained in
44 details.
45
46 Kerwin.

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-user] Re: Understanding new ruby dependencies Chris Stankevitz <chrisstankevitz@×××××.com>