Maybe i wasnt using the correct terminlogy, that having been done by
years of explaining such concepts to people that dont know what
binaries are and english not being my first language.
Nevertheless, VS is using one version of ruby with one set of gems and
running the other version which doesnt happen to have those set of
gems, and this happened by following your advice. That is what i was
trying to say.
so, here are my 2 cents. use defaults for starters, dont go for the
installing in som/weird/place/, have one version of ruby and one set
of gems, like this you are less likely to run into these problems.
> make sure you are calling the correct gem from the correct place. If i
> were you, i would uninstall one of your ruby instalations (at this
> point 1.8)
That's all together not necessary. I suspect all of my development
systems have two ruby installs. I ignore the one that came with the
system and install my own whereever I want. I update my bashrc so it
knows about my intentions and that's about it.
The problem here is that's not what happened. Rather than using bashrc
etc.. to put one install of ruby ahead of the other, ruby1.9 was
renamed to ruby without gem1.9 being renamed to gem (and similarly
for all other ruby related binaries (eg irb))