Take a look at the following Rails ticket: http://dev.rubyonrails.org/ticket/2346
Will this be fixed now with all of new enhancements and reworking of the rubygems code? It's not really a concern of mine, but since I'm going through old Rails tickets I figure I'd see if it was a known issue and if so if it has been addressed. V/r Anthony Eden -- Cell: 808 782-5046 Current Location: Melbourne, FL _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
