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