[gentoo-user] Re: RUBYOPT=-rauto_gem
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
[gentoo-user] Re: RUBYOPT=-rauto_gem
On Sun, 15 Jan 2012 22:21:30 -0800, Hilco Wijbenga wrote: On 15 January 2012 18:21, Michael Orlitzky mich...@orlitzky.com wrote: On 01/15/2012 05:24 PM, Hilco Wijbenga wrote: Hi all, The dev-ruby/rubygems ebuild adds -rauto_gem to the global RUBYOPT. This breaks my own scripts so I have removed it from /etc/env.d. So far, so good. Try asking on the -dev list, or filing a bug. They'll just close it if it's considered invalid. Agree, if things are broken then please file a bug. We have too many open bugs already so I'll wait until (hopefully) I see a few more responses before I file a bug. That way there's less chance of an invalid bug and I may save some valuable dev time. If you want to help us then open a bug so there can be a focused discussion, especially if things are broken. If you really want to help us then participate in the bugs and help us close them :-) Kind regards, Hans
