From: "J. D." Date: 2009-06-03T06:52:34+09:00 Subject: Re: Rubygems Luis Lavena wrote: > On Jun 2, 10:09�am, "J. D." wrote: >> > RubyGems gem commands and Ruby ones are using @"ruby" to refer to the > executable. > > So if there is a C:\Ruby\bin in the PATH (and is not your backup one), > will be used. > > Also, it will try find "ruby" in the current directory and THEN in the > PATH. > > Can you paste the output of "gem env" in both cases? > > Thank you. Hi Luis, I tested with 3 different installations and you are correct. It listed the gem sources properly for each of those folders. When I confirmed the original earlier it happened while I was running QSetup (a program installer) which housed a complete compiled version of my 1.9.1 installation. I was testing whether or not the program installer for my version would function properly. As it contains the devkit and a lot of rubygems it was a huge undertaking. I completely forgot that I was running the installer file and that it was copying source into the C:\Ruby\bin folder. Therefore the gems had not finished compiling and so it showed version 1.3.1. Once the installer completed, the correct version was listed 1.3.4 and all gems showed up under the list. I cannot duplicate the issue I had earlier so I can only assume that it had something to do with the additional installer running behind the scenes. All is well and I appreciate both of you responding to this. I just wanted to make sure I understood how the processes were supposed to work. You confirmed it for me nicely. My thanks. -- Posted via http://www.ruby-forum.com/.