From: Luis Lavena Date: 2007-11-22T02:31:31+09:00 Subject: Re: RubyGems 0.9.5 On Nov 21, 10:52 am, Laurent Sansonetti wrote: > On Nov 21, 2007 10:12 AM, Sylvain Joyeux > wrote: > > Maybe because they would have to do that for every conceivable shell > > lying around ? It does not seem practicle to me. In my opinion, the > > right solution would have been to make RubyGem read a global > > configuration file in /etc which defines sensible GEM_HOME and GEM_PATH > > values. Relying on environment variables is not doable system-wide. > > I also agree with this, it would be nice if RubyGems was reading a > system-wide configuration file as well as environment variables. > System-wide? /etc/gemrc? That seems inpractical and forces another check *if* you're in a *nix environment and the FHS layout exist (which is not the case for distros like GoboLinux). > Maybe the 1.9 integration will provide a way to set default values for > these variables at build time. RubyGems on 1.9 is like irb: they run out of the box with data stored in lib/ruby/1.8 Why this should behave differently? What I see that have potential is have the scripts installed by rubygems and the gems itself relocatable (using GEM_HOME and GEM_PATH), in that way you can replace your ruby+rubygems version and still be able to use gems. Like multi-ruby without duplicated files all over the place. As example of best practices, I plan to test that for Ruby on Windows and submit patches and documentation about the changes ;-) -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi