You probably meant
If you gem env does not have the path that ruby refs
I had something similar on a VPS host recently at RailsPlayground
where they just put a symbolic link to the 'Enterprise' Ruby in
/etc/local bin in place of the ruby executable there. Much confusion
resulted about adding gems into the wrong Ruby and such. I have since
added this line:
PATH=/opt/ruby-enterprise-1.8.7-2009.10/bin:$PATH
to /etc/profile (to add it into the path for every user but root) and
to /root/.bash_profile (to add it into the path for root).
So far it has worked to keep all users pointed to the correct ruby
and gems, but I just did it yesterday. Does that seem like a good
thing to you Linux gurus?
Scott
At 08:19 AM 2/28/2010, you wrote:
I ran into this issue when switching to ruby 1.9 and getting my
paths mixed up.
Compare:
ruby -ve 'p Gem.path'
gem env (look for the GEM PATHS)
If you gem env does have the path that ruby refs, create a symbolic link:
ln -sf /path/to/gem/env/path /path/to/ruby/gem/path
This worked for me, so hopefully with works for you.
On Sat, Feb 27, 2010 at 3:48 PM, Kevin Baker
<<mailto:[email protected]>[email protected]> wrote:
... after moving my app to a new server. All my gems are installed.
If I add new "require" statements for various packages, works fine.
Is there something I am missing as far as environment? Hoping there
is some sort of "classpath" kind of issue.
--
SD Ruby mailing list
<mailto:[email protected]>[email protected]
http://groups.google.com/group/sdruby
--
SD Ruby mailing list
[email protected]
<http://groups.google.com/group/sdruby>http://groups.google.com/group/sdruby
--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
