I read about Gem::Specification being deprecated soon; however, the
copious errors that I’m getting (from the many gems I use) is fast
becoming a pain in the a**. With that said, is there a way I can
temporarily silence this warning?
thanks… 
On May 19, 2011, at 13:10 , Forrest Aldrich wrote:
I read about Gem::Specification being deprecated soon; however, the
copious errors that I’m getting (from the many gems I use) is fast
becoming a pain in the a**. With that said, is there a way I can
temporarily silence this warning?
temporarily you can redirect stderr to /dev/null like so:
blah.rb 2> /dev/null
but I don’t recommend that. I recommend permanently silencing the
deprecations like so:
gem pristine --all --no-extensions
then gem list so see what is left and then individually do the easy
ones:
gem pristine gem_with_binary_but_no_build_args …
(if they’re all easy (ie, no build args), you can just do --all and be
done with it).
Finally, do the ones with build args:
gem pristine gem_with_binary_and_build_args – build_args
On Thu, May 19, 2011 at 10:39 PM, Ryan D. [email protected]
wrote:
gem pristine --all --no-extensions
Not that I asked the original question, but this one saved my day.
Thx to both of you
Cheers
Robert