1 |
On Sat, 07 Jun 2014 17:20:22 -0700, walt wrote: |
2 |
|
3 |
> On 06/07/2014 12:56 AM, Hans de Graaff wrote: |
4 |
|
5 |
> For example, I (want to) use only ruby19: |
6 |
> |
7 |
> #grep RUBY /etc/portage/make.conf RUBY_TARGETS="ruby19" |
8 |
|
9 |
Yes, in hindsight I think that should have been the current default since |
10 |
ruby19 has the best overall coverage for packages. Once ruby20 has caught |
11 |
up I think we'll move to a default of RUBY_TARGETS="ruby20" |
12 |
|
13 |
> In spite of that, portage often insists on installing other versions of |
14 |
> ruby, rdoc, rubygems, and you already know the others. |
15 |
|
16 |
Partially this was because we tried to solve another issue when ruby20 |
17 |
went stable. I removed those forced use flags for ruby20 last week, so |
18 |
this should no longer happen. We still need to come up with a good plan |
19 |
when the same issue will pop up for ruby21. |
20 |
|
21 |
> AFAICT, the other versions of ruby are dragged in by old ruby packages |
22 |
> that were installed before I started using "RUBY_TARGETS" (because I |
23 |
> didn't yet know about RUBY_TARGETS), |
24 |
|
25 |
Yes, these will still have other ruby targets recorded and thus also |
26 |
request them for their dependencies. emerge --newuse should be able to |
27 |
help here. |
28 |
|
29 |
> I discovered all of this by grepping for ruby in /var/db/pkg but it took |
30 |
> me a long time to get it sorted out, and I don't expect that a gentoo |
31 |
> beginner could do it. (OTOH maybe a gentoo beginner wouldn't care about |
32 |
> installing multiple ruby versions :) |
33 |
|
34 |
We try to keep the default settings so that someone who doesn't care or |
35 |
know about ruby should get a good experience. Moving from ruby18 to ruby19 |
36 |
we did some things that could have been handled better (such as not |
37 |
mentioning that the new ruby must be eselected before making the switch), |
38 |
so hopefully we've learned from those when we do the next update. |
39 |
|
40 |
Hans |