New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't work #2
Comments
ruby and irb are not provided by the Gemfile, and thus, were never considered candidates for usage by noexec. I've added ruby and irb to a list of bins permitted to load the Gemfile. I've bumped the version and released this. Let me know if it's fixed. |
Doesn't work for me either: $ echo $RUBYOPT |
So, I've added include/exclude lists that you can add to the processing of this. Take a look at the readme. @YAGoOaR what are you trying to do there? |
Also, running with NOEXEC_DEBUG=1 will print out some illuminating stuff |
I try to run a rake task, in a directory where bundle exec is needed. |
For some reason my Ruby (vanilla 1.9.3) doesn't pick up |
@rkh noexec just got merged to rubygems-bundler, please try with:
and check instructions in readme: https://github.com/mpapis/rubygems-bundler |
the stable version of rubygesm-bundler 0.9.0 was released, the |
the code was merged into https://github.com/mpapis/rubygems-bundler please open any issues in there |
Gemfile
andGemfile.lock
are in pwd.The text was updated successfully, but these errors were encountered: