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

Remove bad advice #128

Merged
merged 2 commits into from Nov 20, 2017
Merged

Remove bad advice #128

merged 2 commits into from Nov 20, 2017

Conversation

pboling
Copy link
Contributor

@pboling pboling commented Mar 26, 2017

Trick to not need to add bundle exec to commands if you add 2 lines to the Rakefile is flawed.

Multiple versions of rake

It does not help at all if you have multiple versions of rake installed.

∴ rake
rake aborted!
Gem::LoadError: You have already activated rake 12.0.0, but your Gemfile requires rake 11.2.2. Prepending `bundle exec` to your command may solve this.
∴ gem list rake

*** LOCAL GEMS ***

rake (12.0.0, 11.2.2, 11.1.2, 10.5.0, 10.4.2, 10.1.0, 10.0.4, default: 0.9.6)

Different Package Manager

It prescribes rubygems which is but one among several options for package managers.

Other use cases

Not all roads lead through the Rakefile, and sometimes bundle exec may still be required. Better to keep things consistent. If it is trouble to type so much shell aliases are an alternative.

the trick to not need to add `bundle exec` to commands if you add 2 lines to the Rakefile is flawed.
@nickcharlton nickcharlton merged commit dcfac43 into thoughtbot:master Nov 20, 2017
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

Successfully merging this pull request may close these issues.

None yet

2 participants