<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>160809</bug_id>
          
          <creation_ts>2007-01-08 00:20 0000</creation_ts>
          <short_desc>sci-geosciences/grass and dev-ruby/rubygems collision in /usr/bin/gem</short_desc>
          <delta_ts>2007-01-29 02:02:51 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Applications</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>reiga@dspnet.fr.eu.org</reporter>
          <assigned_to>nerdboy@gentoo.org</assigned_to>
          <cc>maris.gis@gmail.com</cc>
    
    <cc>ruby@gentoo.org</cc>
    
    <cc>sci-geosciences@gentoo.org</cc>

      

      
          <long_desc isprivate="0">
            <who>reiga@dspnet.fr.eu.org</who>
            <bug_when>2007-01-08 00:20:33 0000</bug_when>
            <thetext>After installing the new version of grass, I was surprised to see that the command &apos;gem&apos; (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:  
&gt; 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.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jakub@gentoo.org</who>
            <bug_when>2007-01-08 00:22:52 0000</bug_when>
            <thetext>(In reply to comment #0)
&gt; After installing the new version of grass, I was surprised to see that the
&gt; command &apos;gem&apos; (from ruby) was not responding the way it did before. 

Hint: stick collision-protect to your FEATURES ;)
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>pclouds@gentoo.org</who>
            <bug_when>2007-01-26 15:49:37 0000</bug_when>
            <thetext>What should be the solution for this? Rename either grass&apos; gem or rubygems&apos; gem, or block each other?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>reiga@dspnet.fr.eu.org</who>
            <bug_when>2007-01-26 19:31:41 0000</bug_when>
            <thetext>(In reply to comment #2)
&gt; What should be the solution for this? Rename either grass&apos; gem or rubygems&apos;
&gt; gem, or block each other?
&gt; 

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
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>maris.gis@gmail.com</who>
            <bug_when>2007-01-28 21:08:43 0000</bug_when>
            <thetext>*** Bug 159969 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>nerdboy@gentoo.org</who>
            <bug_when>2007-01-29 02:02:51 0000</bug_when>
            <thetext>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.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>