I believe per-user gems is now the default
That's right - now if you sudo install a system wide gem, if not, it
just creates a .gems in your home dir and installs there. Of course, the
local gems are only available to Ruby apps running as that user.
Cheers,
Sidu.
Thibaut Barrère wrote:
Per-user gems should not be the default. In RubyInstaller (mingw MRI), as well
as MRI on Linux, and I believe OS X, system-wide gems are
the default. This, of course, would require elevation (sudo gem install xxx).
I believe per-user gems is now the default (it wasn't in the past, but
if I'm right a rubygems update changed that behaviour. Maybe 1.3.0 -
http://rubyforge.org/forum/forum.php?forum_id=27728 => 'RubyGems now
installs gems into ~/.gem if GEM_HOME is not writable. Use
--no-user-install command-line switch to disable this behavior.').
Here's what happens on my machine (OS X):
~$ gem list | grep less
~$ sudo gem list | grep less
~$ gem install less
(...)
~$ gem list | grep less
less (1.2.21)
~$ sudo gem list | grep less
(empty)
~$ gem -v
1.3.5
~$ ruby -v
ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-darwin10.0.0]
-- Thibaut
_______________________________________________
Ironruby-core mailing list
Ironruby-core@rubyforge.org
http://rubyforge.org/mailman/listinfo/ironruby-core
_______________________________________________
Ironruby-core mailing list
Ironruby-core@rubyforge.org
http://rubyforge.org/mailman/listinfo/ironruby-core
