Just noticed this:

Gregory Brown wrote:
> This patch seems to resolve the problem, also:
> 
> --- rubygems.rb 2006-06-13 22:48:48.000000000 -0400
> +++ rubygems-fix.rb     2006-06-13 22:49:22.000000000 -0400
> @@ -164,7 +164,7 @@
> 
>        # Load dependent gems first
>        spec.dependencies.each do |dep_gem|
> -       activate(dep_gem, autorequire)
> +       activate(dep_gem, spec.autorequire)
>        end

Oh, don't do this.  The autorequire field in the gem spec is not a 
boolean flag, but the name of the file to automatically require when 
activating a gem.  Setting autorequire in the gem spec only controls 
what file you want to autorequire, not whether dependent gems should 
autorequire or not.

And we are deprecating autorequire anyways.

-- Jim Weirich

-- 
Posted via http://www.ruby-forum.com/.