Globally disable without config? about mail_safe HOT 3 CLOSED

If you don't want mail safe to do anything, don't require it.

from mail_safe.

Bundler is pretty much the de-facto standard, and you can't exclude a named group as far as I know. Requiring a gem that has potentially dangerous side-effects might be something worth mulling over...

from mail_safe.

Bundler is pretty much the de-facto standard, and you can't exclude a named group as far as I know. Requiring a gem that has potentially dangerous side-effects might be something worth mulling over...

I agree. That's why you shouldn't be auto-requiring any gems.

There are three solutions you can use with bundler:

• Use Bundler.setup rather than Bundler.require. setup sets up your load path but does not auto-require gems. I think it's the best way to use bundler anyway...I really dislike bundler's auto-requiring functionality. It's a great way to get an app with really slow boot times.
• Use Bundler.require(:group1, :group2), and put put mail_safe in one of the other groups.
• add :require => nil to the gem declaration in your Gemfile.

from mail_safe.