lasitha
3/4/2009 7:00:00 PM
On Wed, Mar 4, 2009 at 11:55 PM, Tom Cloyd <tomcloyd@comcast.net> wrote:
>
> the consensus appears to be:
>
> 1. the "gem clean" command is broken, at least some of the time. For me, in
> my environment, all the time.
> 2. the "workaround" is to uninstall each gem and reinstall it. With about 25
> gems installed, that definitely a delightful prospect. It's even worse when
> one considers that, as I documented in my original email, the 'gem
> uninstall' command is also broken.
>
As Eric noted, the trouble comes about when you have multiple
repositories. There may be good reason for such a setup, but if there
isn't _and_ most of your outdated gems are in one of them, you could
just blow that one away (rm -rf).
In my case the only reason i've had multiple repos is when i forget to
sudo and end up with gems in ~/.gem. I've blown that one away a
couple times and that hasn't bothered rubygems any, as far i can tell.
Cheers,
lasitha.