Skip to content
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

v3: Should not be using "bundler --binstubs" #345

Open
archseer opened this issue Sep 26, 2013 · 1 comment
Open

v3: Should not be using "bundler --binstubs" #345

archseer opened this issue Sep 26, 2013 · 1 comment

Comments

@archseer
Copy link

See https://gist.github.com/chrismo/5043420. This is why you were having problems with the binstubs overwriting the rails default ones.

I think the script/bootstrap should be modified to generate binstubs only for a select list of gems here.

Anyone that has already bootstrapped the project should manually edit their .bundle/config, because bundler remembers the --binstubs option and generates binstubs again any time you run bundler again.

Since we generate the binstubs as a part of the bootstrapping process, I think we can remove them from version control. They'll get regenerated any time one runs script/bootstrap anyway.

@archseer
Copy link
Author

(We actually don't seem to be using much of the binstubs anyway, for instance bin/unicorn could replace bundle exec unicorn et cetera)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant