| 1 |
On 05/22/2012 09:10 PM, Chris Stankevitz wrote: |
| 2 |
> |
| 3 |
> How was I supposed to learn the "proper" way of dealing with this |
| 4 |
> RUBY-related system change? |
| 5 |
|
| 6 |
The way I learned was by watching the emerge output: |
| 7 |
|
| 8 |
$ emerge -pv dev-ruby/rails |
| 9 |
|
| 10 |
These are the packages that would be merged, in order: |
| 11 |
|
| 12 |
Calculating dependencies... done! |
| 13 |
[ebuild N ] app-admin/eselect-rails-0.16 2 kB |
| 14 |
[ebuild N ] dev-ruby/tmail-1.2.7.1-r2 USE="-debug -doc -test" |
| 15 |
RUBY_TARGETS="ruby18 -jruby -ree18" 436 kB |
| 16 |
|
| 17 |
and wondering, "RUBY_TARGETS, what the hell is that?" |
| 18 |
|
| 19 |
I'm sure there's a proper way, but that's the way I've discovered all of |
| 20 |
the USE_EXPAND variables. LINGUAS was the first, then I noticed |
| 21 |
ALSA_CARDS, APACHE2_MODULES, XFCE_PLUGINS... |
| 22 |
|
| 23 |
The default list can be found in, |
| 24 |
|
| 25 |
/usr/portage/profiles/base/make.defaults |
Archives