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