On Feb 6, 2009, at 12:00 AM, Toby wrote:
So the moral of this story is if you're a Ruby developer who uses MacVim, _don't_ remove /System/Library/Frameworks/Ruby.framework. You can remove /Library/Ruby, and point /usr/bin/ruby etc at your local version. Just leave the Framework there and MacVim is happy, and no issues with conflicting ruby versions either.
Just throwing in some unsolicited advice here, but You're Doing It All Wrong™. Stuff in /usr/bin and *especially* /System is for the system and the system alone. Your custom symlink will quite likely be overwritten in a future software update. MacVim isn't the only thing that will break when removing the system ruby framework.
The correct way to install a custom ruby is to put it in /usr/local or /opt/local—as you have—and then put /usr/local/bin in your PATH before /usr/bin. Then your custom version will be the one found by default when you run ruby, but nothing that relies on the system version in /usr/bin or /System will break.
Don't fight the system, and it won't fight you :) Jason
smime.p7s
Description: S/MIME cryptographic signature
