On 28.11.2007, at 19:36, Noah M. Daniels wrote:
Interestingly, the words "major problems" and "Leopard" coincide a
lot
lately.
For what it's worth, I've had zero problems with the Apple-supplied
ruby, rails, etc...
Frankly, knowing that everything works well for others isn't worth
much to people who _are_ having problems ;)
But it appears to be a common reaction – especially in the Apple
community.
I would recommend sticking with the Apple-supplied
ruby; for once they've gotten it right, and everything seems to work
beautifully.
You must have a different understanding of 'getting it right'. Here's
what I got when I entered 'ruby -v' or 'gems' into the console of a
fresh 10.5 install:
-bash: ruby: command not found
After getting it to work eventually, a 'gem update --system' just
wrecked the whole Ruby installation. At that point I just gave up and
installed Ruby/Gems and Rails via Macports.
One thing I'd really like to know is how one is supposed to update the
Ruby/Rails packages which shipped with Leopard. I had no chance to
check, but are they still shipping Rails 1.1.2? I bet that Apple isn't
going to update Ruby during the whole lifetime of Leopard. Anything
else would be a big surprise.
So here goes my advice again: Use Macports. Do not use whatever Apple
ships.
Cheers,
Andy
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk
