| 1 |
On 10/12/2013 20:28, Bruce Hill wrote: |
| 2 |
> On Tue, Dec 10, 2013 at 05:52:36PM +0200, Alan McKinnon wrote: |
| 3 |
>> |
| 4 |
>> The only thing portage can do is assume you want everything to work |
| 5 |
>> under all installed interpreters. If you want to restrict the list of |
| 6 |
>> installed interpreters, use the relevant settings in make.conf. Python |
| 7 |
>> has PYTHON_TARGETS and SINGLE_PYTHON_TARGET for this, I don't know what |
| 8 |
>> the ruby equivalent is. |
| 9 |
>> -- |
| 10 |
>> Alan McKinnon |
| 11 |
>> alan.mckinnon@×××××.com |
| 12 |
> |
| 13 |
> mingdao@workstation ~ $ grep ruby /etc/portage/make.conf |
| 14 |
> RUBY_TARGETS="ruby20" |
| 15 |
> |
| 16 |
> Can't imagine you didn't know that. Ruby hater? :D |
| 17 |
> |
| 18 |
|
| 19 |
|
| 20 |
You could say that: |
| 21 |
|
| 22 |
$ grep -ir -C1 ruby /etc/portage |
| 23 |
/etc/portage/package.use/package.use- # I see no need for lvm thin |
| 24 |
volumes. And it needs thin-provisioning-tools |
| 25 |
/etc/portage/package.use/package.use: # which needs ruby. I do not want |
| 26 |
ruby. |
| 27 |
/etc/portage/package.use/package.use- sys-fs/lvm2 -thin |
| 28 |
|
| 29 |
|
| 30 |
|
| 31 |
But the real reason I don't have ruby is I don't have a use for it |
| 32 |
|
| 33 |
|
| 34 |
|
| 35 |
-- |
| 36 |
Alan McKinnon |
| 37 |
alan.mckinnon@×××××.com |
Archives