Bugzilla Bug 160809

After installing the new version of grass, I was surprised to see that the
command 'gem' (from ruby) was not responding the way it did before. Of course,
since it had been replaced by another program from grass.


Reproducible: Always

Steps to Reproduce:
1. emerge dev-ruby/rubygems
2. emerge sci-geosciences/grass
3. equery b /usr/bin/gem

Actual Results:  
> equery b /usr/bin/gem
[ Searching for file(s) /usr/bin/gem in *... ]
sci-geosciences/grass-6.2.0 (/usr/bin/gem)
dev-ruby/rubygems-0.9.0-r2 (/usr/bin/gem)


Expected Results:  
well, I expect to have the 2 programs at different places or with a different
name.

(In reply to comment #0)
> After installing the new version of grass, I was surprised to see that the
> command 'gem' (from ruby) was not responding the way it did before. 

Hint: stick collision-protect to your FEATURES ;)

What should be the solution for this? Rename either grass' gem or rubygems'
gem, or block each other?

(In reply to comment #2)
> What should be the solution for this? Rename either grass' gem or rubygems'
> gem, or block each other?
> 

not block each other, because I need both grass and rubygems.

this problem is discussed in the grass ML : 
http://www.nabble.com/GRASS-GEM-and-Ruby-GEM-name-collision-t2940004.html

*** Bug 159969 has been marked as a duplicate of this bug. ***

The Grass Extension Manager (gem) is now installed to /usr/grass62/bin, along
with all the other grass binaries.  Only the grass62 startup script remains in
/usr/bin.  Since Grass tries to manage its own environment, ie, the above Grass
bin directory should *not* be in your path, the Ruby gem binary should always
be found first.