On Tue, 22 May 2012 23:16:00 -0400
Michael Orlitzky <mich...@orlitzky.com> wrote:

> On 05/22/2012 09:10 PM, Chris Stankevitz wrote:
> > 
> > How was I supposed to learn the "proper" way of dealing with this
> > RUBY-related system change?

That change was committed two-and-a-half years ago in the eclass:

http://archives.gentoo.org/gentoo-dev/msg_2305dbeaaf5b02cb74a84c9b06333708.xml

and the Gentoo Ruby project has a section on it

http://www.gentoo.org/proj/en/prog_lang/ruby/index.xml

Actually I learnt the RUBY_TARGETS from flameeyes's blog two years ago

http://blog.flameeyes.eu/2010/02/ruby-ng-package-in-a-bottle-or-learn-how-to-write-a-new-ruby-ebuild

> The way I learned was by watching the emerge output:
> 
>   $ emerge -pv dev-ruby/rails
> 
>   These are the packages that would be merged, in order:
> 
>   Calculating dependencies... done!
>   [ebuild  N     ] app-admin/eselect-rails-0.16  2 kB
>   [ebuild  N     ] dev-ruby/tmail-1.2.7.1-r2  USE="-debug -doc -test"
>   RUBY_TARGETS="ruby18 -jruby -ree18" 436 kB
> 
> and wondering, "RUBY_TARGETS, what the hell is that?"
> 
> I'm sure there's a proper way, but that's the way I've discovered all
> of the USE_EXPAND variables. LINGUAS was the first, then I noticed
> ALSA_CARDS, APACHE2_MODULES, XFCE_PLUGINS...
> 
> The default list can be found in,
> 
>   /usr/portage/profiles/base/make.defaults

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.

Kerwin.

Attachment: signature.asc
Description: PGP signature

Reply via email to