Advice to use bundle exec incompatible with guard-bundler #9

guyboltonking opened this Issue Mar 1, 2012 · 4 comments


None yet
4 participants

(I'm raising this because I haven't found an explicit solution to this issue; the symptoms are those as described in #2 and #3. Commit 61f034e fixes some of the problem, and this comment in issue #2 is the missing link: use bundle install --binstubs).

Guard Issue #223 introduces a warning asking users to execute guard using bundle exec; however, doing this prevents guard-bundler from working.

The solution is to use bundle install --binstubs, and then execute guard using the stubbed version in bin/guard, at which point everything works as intended.

Why? Using bundle exec guard prevents ::Bundle.with_clean_env from working as intended: with_clean_env restores the environment found when Bundler was loaded, but bundle exec has already set RUBYOPT in the environment when guard loads Bundler, so with_clean_env doesn't remove it.

I think the best solution at this point might be some documentation: shall I update the README?

artm commented Mar 19, 2012

I've been bitten by this as well. Yes, documentation should be updated.

Was also hit by this issue. Shouldn't the warning added in 223 also be updated to reflect this issue?


yannlugrin commented Jun 15, 2012

Released version 1.0.0 with cli option, if you want upgrade informations in README, please send another pull requests.

THanks for your investigation.

yannlugrin closed this Jun 15, 2012

Looks like the core issue of ::Bundle.with_clean_env not clearing out RUBYOPT properly was fixed in Bundler 1.1.0 (see carlhuda/bundler#1604), so there's no need for an updated README, as the advice to use bundle exec is now wholly valid for guard-bundler!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment