On Mar 30, 12:01 am, Eric Hodel <drbr...@segment7.net> wrote:
> On Mar 29, 2008, at 15:22 PM, Dave Thomas wrote:
>
>
>
> > On Mar 29, 2008, at 4:50 PM, matt neuburg wrote:
> >> Could someone explain how to do this on Mac OS X 10.5.2? I tried:
>
> >> gem --version
> >> => 1.0.1
>
> >> sudo gem update --system
>
> >> Lots of stuff scrolled by, but afterwards, I still see:
>
> >> gem --version
> >> => 1.0.1
>
> >> This might be related to the fact that
>
> >> which gem
> >> => /usr/bin/gem
>
> >> but the update process reports that gem was installed in
> >> /System/Library/Frameworks/Ruby.framework etc etc etc.
>
> >> Clearly I am just thrashing about here... Thx for any - m.
>
> > I emailed Chad about this: the gem update is installing the gem
> > command into
>
> > /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/
> > bin/gem
>
> > It should go into
>
> > System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/gem
>
> > which is the symlink from /usr/bin/gem
>
> Hrm, this is odd. I had a working RubyGems 1.1.0 on apple ruby when I
> released, but after removing it to restore the apple RubyGems 1.0.1, I
> am again stuck with 1.0.1 like you. Perhaps I did some other monkey-
> business that caused it to work correctly.
>
> I have an idea of what the problem is, but until I figure out exactly
> what the issue is, running:
>
> sudo update_rubygems
>
> installs RubyGems correctly.

And then... someone says "Windows is broken" :-P

Nevermind, just kidding ;-)

Regards,
--
Luis Lavena