>> Ara, do you have any examples of gems that are busted by the current >> behavior? I assume you've run in to a few. > > I patched aasm not that long ago for this reason, it was conflicting with > state_machine
If you have two gems that have a same named library [like mysql.so] then doing a require 'mysql' within one can sometimes require the mysql of the other. -r _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers