added rails to bundled_commands #868

Merged
merged 1 commit into from Feb 21, 2012

Conversation

Projects
None yet
3 participants
Contributor

wgriffioen commented Jan 26, 2012

While switching to a different approach in developing with Ruby (discarding RVM and using rbenv with project specific bundles instead) I found out that rails is not being executed through bundler. This little patch fixes this.

Contributor

eddorre commented Jan 27, 2012

I'd personally like to see this come back in but it was taken out in this pull request (#785).

For the full reasoning behind thing, see this blog post: http://blog.wyeworks.com/2011/12/27/bundle-exec-rails-executes-bundler-setup-3-times.

I've reached out to Santiago on his blog to confirm that 1) The issue will be fixed in the latest release of Bundler and 2) If Rails is not in the load path - meaning it's only installed in the bundle - then there is no issue.

Hopefully Santiago will clear things up soon. In the meantime, we're going to hold this until we can get some definitive answers.

drubin commented Feb 13, 2012

I would also like to see it brought back. A slightly slower command is still better then a non-working command.

I have patched this locally because my rails setup does not work with out sing bundle exec. Multiple rails versions installed using rbenv.

Contributor

eddorre commented Feb 21, 2012

I agree, I'm going to bring this back. Judging from the comment, if I understood correctly, Bundler 1.1 will take care of some of these issues.

eddorre merged commit 631e3d8 into robbyrussell:master Feb 21, 2012

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