I recently installed Ruby 1.8.4 on my iMac, running OSX 10.4. Ruby,
Rails, etc. run great and I am working through Ruby for Rails (great
book, BTW).
I installed ruby in /usr/local so as not to conflict with the version
(1.8.2) used by OSX.
Now, I have to type “/usr/local/bin” before all Ruby commands, and
similar to use rails, rubygems, etc.
This is causing several problems with gems as well, as the Mongrel
webserver (for example) requires 1.8.4, and if you try to install it via
gem it dies - it is smart enough to see the ‘system’ version, but not
the /usr/local version and won’t let you install it on an ‘old’ system.
I tried Google-ing for $PATH configurations, because I know it has to be
a simple fix to let me run “ruby -v” (or whatever) at a prompt pretty
much anywhere and have my system use the /usr/local version (1.8.4)
instead of 1.8.2, but I just can’t figure it out.
Paste of relevant issue from terminal session below, including $PATH in
case I made a non-obvious (to me) error there.
I searched this forum as well, and read through the various installation
guides - if it is there, I missed or misunderstood it. Guidance, even
flames (with a link or winning Google search text), would be welcome.
Beware, updates from 10.x.y to 10.x.z may restore /usr/bin/ruby.
/usr/local/mysql/bin:/bin:/sbin:/usr/bin:/usr/local/bin:/usr/sbin
well the places in the path are tried in order. so just put the
/usr/local/bin before /usr/bin
Thanks for the fast reply - if I read this correctly, I am literally
removing ruby (or irb, etc.) from the path the system ‘sees’ to a
directory it won’t (not on $PATH) so it will eventually default to my
/usr/local version - is this correct?
I understand the mv command - it is the impact on system behavior as it
searches for a path I am asking about - that’s unclear to me.
As Elliot suggests, re-order your path. The system looks for programs
on the path from left to right. So as /usr/bin comes before /usr/local/
bin, the system ruby is found first. So if you move /usr/local/bin in
front of /usr/bin, then your version of ruby will be found first.
I would not modify anything in /usr/bin directly. Apple assumes that
the system /usr/bin is theirs and unmodified and will (and have!) change
things there in updates without warning - possibly breaking your
modifications and potentially causing serious system problems.
Installing in /usr/local and prepending it to your path is the usual
unix way of doing things.
I would not modify anything in /usr/bin directly. Apple assumes that
the system /usr/bin is theirs and unmodified and will (and have!)
change
things there in updates without warning - possibly breaking your
modifications and potentially causing serious system problems.
Installing in /usr/local and prepending it to your path is the usual
unix way of doing things.
Just to speak on this point, I’ve been safely using the replacement
solution for about 6 months now with no trouble at all. But the one
thing I did after I moved /usr/bin/ruby is to make a link from /opt/
local/bin/ruby (my darwinports installation) to /usr/bin/ruby.
Pathing works most of the time, but I had some problems with RadRails/
Eclipse because it doesn’t appear to honor pathing provided
in .profile or .login. Which prompted the linking solution. It’s a
little ugly and might go away with future updates, but it was about
all I had left for a few programs that ignored my personal path
information.
-Mat
On Saturday, July 15, 2006, at 12:37 PM, Mat S. wrote:
solution for about 6 months now with no trouble at all. But the one
thing I did after I moved /usr/bin/ruby is to make a link from /opt/
local/bin/ruby (my darwinports installation) to /usr/bin/ruby.
Pathing works most of the time, but I had some problems with
RadRails/Eclipse because it doesn’t appear to honor pathing provided
in .profile or .login. Which prompted the linking solution. It’s a
little ugly and might go away with future updates, but it was about
all I had left for a few programs that ignored my personal path
information.
Sometimes modifying /usr/bin is the only option left - but sooner or
later an Apple update will break it. (I guess the last time this
happened was a little over 6 months ago if you haven’t been hit by it).
So I suggest that the OP try everything else first.
But, as you have discovered, sometimes you have to choose the less
optimal solution.