Thanks Jim, looks like David already merged it in, I'm planning on moving around the gem code a bit internally tonight and then getting a new version out that doesn't stomp all over constants like a whiny kid wanting ice cream.
As for gem plugins in general, what's the best way to get around this in the future? Perhaps for testing we can have something like GEM_LOAD_PLUGINS = false require 'rubygems' # No plugins are loaded Or better yet, only load plugins when gem commands are run and not when rubygems is required. Thoughts? -Nick On Fri, Aug 21, 2009 at 3:02 PM, Jim Weirich <jim.weir...@gmail.com> wrote: > > On Aug 21, 2009, at 9:43 AM, Nick Quaranto wrote: > > That constant should definitely be namespaced, I'll get a new version out >> today that doesn't do that. I have seen this behavior and it's made >> testing >> the gemcutter gem hard, since I have to uninstall all local versions in >> order to get my working copy loaded. >> > > Nick, I sent you a pull request on github. > > > -- > -- Jim Weirich > -- jim.weir...@gmail.com > > _______________________________________________ > Rubygems-developers mailing list > http://rubyforge.org/projects/rubygems > Rubygems-developers@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers > _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
