On Sun, 15 Jan 2012 14:24:30 -0800, Hilco Wijbenga wrote: > If there is a requirement for this to be in the global environment, what > is the consequence of unsetting RUBYOPT in my own .bashrc (or similar)? > Is that "safe"? Or does that break something that I simply haven't > noticed yet?
We don't support that setup, but you can always try. The only consequence should be that scripts won't find code installed by rubygems, unless you explicitly require 'rubygems' yourself. The reason for this is partly history, and we can't really change it now without breaking a lot of stuff. It it also there to provide more choice, since you don't need to be explicit about this in your scripts. Finally, this is the default in ruby 1.9, even without RUBYOPT set, so we now have a matching situation between the different ruby versions. Kind regards, Hans
