-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi again,
NAKAMURA, Hiroshi wrote: >> This is fixed in latest RubyGems. If the LoadError file does not >> match the original feature, the exception is re-raised immediately. > > Sorry, I was not aware the change. > > Hmm. Isn't that a bit too strict? Gem A depends to Gem B, but the > author of Gem A accidently removed a dependency to Gem B from its > gemspec. Now users get a LoadError even though they actually have a Gem > B. Right? Never mind. I was wrong. Subsequent require should handle this situation as we expected. Regards, // NaHi -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) iQEVAwUBRyxBsh9L2jg5EEGlAQLJIgf+K/5BdaVDt9L8n1yr9wA8U9kefPZ7nF5d gFnGEwaTxlcnk6MzN+axyS0pJ644Iqg9c1JOMECMy7p1LSp4yqEk17Ptk9Gy9ta/ I6eGhz76gL7AQAwfmhAryUbknxo+FXasdezHYUTxgxzjptgD8ZhDQYB5QFR1EzxX xgINhUs55Sm+OrgcXmwitXkz+bH/ZiEarSQ7rd4GuwGXSxuvXxxyYhFudgeANREj zAi5dXJZeeqX7GXJW+n7zm20LnHQeLPh0ndeLqolqu+4U4WEKmoR6lQKOZ+o0xJ6 XH9OXj/O+uqi8upRgy7p4dw4NkCA+eFLK3hyoks5zqE5ya4ZLyS2qg== =TUVU -----END PGP SIGNATURE----- _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
