-
Notifications
You must be signed in to change notification settings - Fork 7
Disabling warnings
Cezary Baginski edited this page Aug 2, 2016
·
1 revision
NOTE: Please be responsible and proactive if you decide to disable warnings.
- It's much cheaper and less stressful to try and upgrade your Ruby sooner.
- If there are problems with a new version, it's better to report bugs before so they're fixed by the time you're forced to upgrade
- Usually, you'll avoid lots of bugs by upgrading - and we rarely appreciate problems we never know we've avoided
- There are often lots of speed and memory optimizations - which may mean lower hosting costs for your business
- The sooner the Ruby community upgrades to a newer Ruby, the easier it will be for contributors to focus on making Ruby better
- The more people stay up to date, the faster Ruby can evolve and stay not only relevant, but be a great technical decision for your business and a great investment into a technology that is both mature and also fast-evolving
So consider the warnings as being there to protect your precious time and your business in the long run.
Just set the following in your shell/server configuration:
export RUBY_DEP_GEM_SILENCE_WARNINGS=1
Or, you can add this at the top of your Gemfile
:
ENV['RUBY_DEP_GEM_SILENCE_WARNINGS'] = '1'
At that point, RubyDep shouldn't create any output (unless it crashes for some reason).
You can require the file directly in your Gemfile
:
gem 'ruby_dep', '~> 1.4', require: 'ruby_dep/quiet'
or early in your sources:
require: 'ruby_dep/quiet'