Certainly, I've found it very convenient on a mostly-non-ruby project, to use JRuby and local JRuby gems, with a completely standalone install for each instance of the main project (I actually have the whole JRuby directory checked in to Subversion).
This means that (say) on my Hudson CI server, I can have different versioned jruby+gem setups for building the trunk and for each branch, with no risks of building against a different version than intended. I can definitely see the appeal of doing something similar with 'real' ruby. On a side note - I'm not a big fan of macports at all - I seem to regularly run into pain, like last week, where in attempting to upgrade ImageMagick I managed to break everything, and lost 4+ hours of my life struggling to fix it, which included downloading a new XCode and then reinstalling macports from scratch - and even then, the Gimp failed to build. I want my Ubuntu back :) - Korny On Wed, Sep 30, 2009 at 2:23 PM, Ben Hoskings <[email protected]> wrote: > > On 30/09/2009, at 11:46 AM, Alan Harper wrote: > >> I also had the same issue as Dr Nic, I >> don't like messing with my system ruby on OS X > > I'm interested in your rationale (and others' too) on setting up ruby > — I'm not sure what you mean here, since "not messing with the system > ruby" is why I install a separate copy. > > My problem with using the system-installed ruby is that every time you > "sudo gem install", you're changing the base system. There's a really > good writeup in the homebrew README under "Don't sudo": > http://github.com/mxcl/homebrew > > Briefly, there are two advantages to not sudoing for package and gem > installs: > - It puts commandline applications on the same footing as OS X apps, > which are installed without privileges by dragging them into / > Applications. > - Not sudoing means you know for a fact that you're not changing the > base install. You can delete /usr/local and your system is new again. > > I agree that macports is not the best answer, but it's always done the > job for me (after a slow initial build :) ). I'm going to spend some > time ASAP finishing the homebrew support in babushka, which should > make the process a lot cleaner (and faster, since it links against > system libraries instead of building duplicates). > > Homebrew has excellent support for installing multiple concurrent > versions of the same package, like rubygems, which I think will come > in handy when we all start using 1.9 more. There's also RVM — I'm not > sure which will be a better choice for this because I haven't looked > into it very far. Either way though, I think installing a separate > ruby in order to leave the system untouched is the way to go. > > Interested to see what everyone thinks about this. "With our powers > combined" and all that :) > > - Ben > > > > > -- Kornelis Sietsma korny at my surname dot com kornys on twitter/fb/gtalk - korny on wave sandbox "Every jumbled pile of person has a thinking part that wonders what the part that isn't thinking isn't thinking of" --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~----------~----~----~----~------~----~------~--~---
