breaks rails new about rubygems-bundler HOT 8 CLOSED

please test with:

gem install rubygems-bundler --pre
NOEXEC=0 rails new app

It will basically not load Gemfile from current directory to use rails, and everything will work correctly, I have added a test case for it: https://github.com/mpapis/rubygems-bundler/blob/1.0.0/test/dtf/rails_and_gemfile_comment_test.sh

from rubygems-bundler.

Good thanks!
I installed

$ gem install rubygems-bundler --pre  ( 1.0.0 beta5 )

which prompted me to

$ gem uninstall -ax rubygems-bundler -v 0.9.2

next, I reset my .gemrc to include

custom_shebang: $env ruby_noexec_wrapper

and then I reset my wrappers with

$ gem regenerate_binstubs                                   

Now, the result:

$ rails new app                      # => no Gemfile.lock
$ NOEXEC=0 rails new app  # => Gemfile.lock created

from rubygems-bundler.

you do not need the .gemrc part anymore:

custom_shebang: $env ruby_noexec_wrapper

this is now automated.

from rubygems-bundler.

Wow! --- better and better!

from rubygems-bundler.

How I discovered it:
I am running with .railsrc set to --skip-bundle and -m pointing to my template generator.
My template generator builds the Gemfile, then runs bundle, and finally runs further generators in the app.
Now, with a global NOEXEC=0, won't these generators need a bundle exec prefix in my template?

from rubygems-bundler.

I'm not sure at all, basically after the directory is changed to the new project dir you could do one of this two things:

unset NOEXEC
NOEXEC=1

from rubygems-bundler.

my script starts off like this...

  ## check env for NOEXEC=0 
  unless  ENV[ 'NOEXEC' ] == '0'
    say '==> please set NOEXEC=0 to run this script'
    exit
  end
  # great, now unset it.
  ENV[ 'NOEXEC' ] = nil

looks clumsy, but it works

from rubygems-bundler.

this made me laugh, maybe better add a comment explaining it is needed because of calling rails in context of wrong Gemfile, I would drop the code first time I would see it in my project

from rubygems-bundler.