From: Luis Lavena <luislavena@...>
Date: 2008-08-02T19:35:42+09:00
Subject: Re: RubyGems - update made a mess - help needed with Windows

On Aug 1, 11:27 pm, Becca Girl <csch...@yahoo.com> wrote:
> Ryan Davis wrote:
> > I don't use windows... buyer beware.
>
> > I think you should remove that bat file and anything else rubygems in
> > the same directory and repeat steps 2-3 in Luis' instructions. If the
> > problem persists, then something is legitimately fubar in rubygems (I
> > doubt it--Luis has been awesome helping with windows support).
>
> This is the list of files that appear to be related to rubygems.  Do I
> delete all of these files and then repeat steps 2-4?
>
> gem
> gem.bat
> gemhelp.bat
> gemlock
> gemlock.bat
> gemlock.cmd
> gemri
> gemri.bat
> gemri.cmd
> gemwhich
> gemwhich.bat
> gemwhich.cmd
> gem_mirror
> gem_mirror.bat
> gem_mirror.cmd
> gem_server
> gem_server.bat
> gem_server.cmd

Those files are left-overs of previous version of rubygems, you can
safely remove those and install RubyGems on top which will only create
gem and gem.bat for you.

On the rake issue, the require_gem was deprecated as Ryan commented,
but also the rake.cmd file you had was old.

This can be easily solve by removing the old gem of rake and
reinstalling it again.

gem uninstall rake

and then:

gem install rake

If you find other problems when you call some gems directly, is mostly
because you have a old batch file (.bat or .cmd).

Hope this helps and please apologize the delay on my reply.
--
Luis Lavena