[ruby-core:31031] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9

Hi,

2010/7/3 Evan Phoenix <[e-mail]>:
> I've updated the patch to pass test-all. There is a rubygems test for this bug, but it can't run properly because test-all runs under miniruby, which has no prelude, so I've disabled the test for now.
>
> This patch runs test-all fine, and demonstrates the fact that using "require 'rubygems'" restores the system to 1.8 behaivor, therefore avoiding this bug.

Great.  I confirmed it indeed runs test-all.
But it emits some "already initialized constant" warnings.
It seems to allow to require "rubygems" twice.  Is it ok?
If there is no objection, I'll commit this patch.


$ make test-all
./miniruby -I./lib -I.ext/common -I./- -r./ext/purelib.rb
./tool/runruby.rb --extout=.ext  -- "./test/runner.rb"
/home/mame/work/ruby_1_9_2/lib/rubygems.rb:108: warning: already
initialized constant VERSION
/home/mame/work/ruby_1_9_2/lib/rubygems.rb:108: warning: already
initialized constant RubyGemsVersion
/home/mame/work/ruby_1_9_2/lib/rubygems.rb:152: warning: already
initialized constant MUTEX
/home/mame/work/ruby_1_9_2/lib/rubygems.rb:154: warning: already
initialized constant RubyGemsPackageVersion
/home/mame/work/ruby_1_9_2/lib/rubygems.rb:160: warning: already
initialized constant WIN_PATTERNS
/home/mame/work/ruby_1_9_2/lib/rubygems.rb:1023: warning: already
initialized constant MARSHAL_SPEC_DIR
/home/mame/work/ruby_1_9_2/lib/rubygems.rb:1028: warning: already
initialized constant YAML_SPEC_DIR
Loaded suite ./test/runner
Started


I'm now happy that everyone is tackling this issue.
I'd be happier if you had done so before rc1 is released :-)

-- 
Yusuke Endoh <[e-mail]>