Bug 320481

Summary:	dev-ruby/rubygems & app-eselect/eselect-ruby drop multiple gem commands
Product:	Gentoo Linux	Reporter:	Diego Elio Pettenò (RETIRED) <flameeyes>
Component:	New packages	Assignee:	Gentoo Ruby Team <ruby>
Status:	CONFIRMED ---
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Diego Elio Pettenò (RETIRED) gentoo-dev

2010-05-18 23:29:45 UTC

Right now we have multiple gem commands in /usr/bin… I guess we really should just drop them, and have a single gem command that uses the selected Ruby by default, just like we have a single rake and so on.

Comment 1 Hans de Graaff gentoo-dev

2010-08-22 08:42:30 UTC

This is now fixed since we always use the unbundled rubygems, right?

Comment 2 Diego Elio Pettenò (RETIRED) gentoo-dev

2010-08-22 11:41:28 UTC

No...


flame@yamato mytmpfs % qlist rubygems | grep /usr/bin
/usr/bin/gem19
/usr/bin/jgem
/usr/bin/gemee18
/usr/bin/gem18

Comment 3 Alex Legler (RETIRED) archtester

2010-08-22 11:46:31 UTC

How would I install a gem for $not_default then?

Comment 4 Alex Legler (RETIRED) archtester

2010-08-22 11:48:26 UTC

(In reply to comment #3)
> How would I install a gem for $not_default then?
> 

doing the -v version, I'd hate having to do ruby18 /usr/bin/gem install..
What's the problem with the current setup?

Comment 5 Diego Elio Pettenò (RETIRED) gentoo-dev

2010-08-22 11:50:15 UTC

Out of line with the  other binaries we install...

ruby19 -S gem install

Or we'll have to make /usr/bin/ruby a binary respecting RUBY variable.