Austin Ziegler <halostatue / gmail.com> writes:
> I'm not going to disagree that RubyGems can't improve its error
> messages; it can. But the reality is that this is not something that
> RubyGems should ever be able to detect and prevent -- especially
> since the error is coming *during the run process* and not during
> the startup (e.g., not during a 'require' stage).

At least in my case (and I believe in the OP's), it *was* during a
'require' stage; specifically, inside
/usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb.  I have not
devled deeply into this code, but it seems like that would be a good
place to intercept this.

-=Eric
-- 
Come to think of it, there are already a million monkeys on a million
typewriters, and Usenet is NOTHING like Shakespeare.
		-- Blair Houghton.