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

Rake-less rubies should not default to system-wide rake #629

Closed
jorgenpt opened this issue Dec 7, 2011 · 0 comments
Closed

Rake-less rubies should not default to system-wide rake #629

jorgenpt opened this issue Dec 7, 2011 · 0 comments
Assignees
Milestone

Comments

@jorgenpt
Copy link

jorgenpt commented Dec 7, 2011

Currently, if you have a Ruby installed that does not have a rake, then it will default to the system-wide rake. On OS X, this means /usr/bin/rake, which is hardcoded to the ruby in /System.

This causes issues as it'll use different gems and different ruby version, but even worse, in combination with Bundler (bundle exec rake) it'll cause Bundler's gems to be loaded alongside the system-wide gems, causing cryptic and hard-to-debug problems (like https://gist.github.com/1440686 ).

Personally, I think rvm should install a wrapper for Rake that tells the user that there is no rake for their current ruby and exits with an error when there is no rake for the current ruby, rather than redirecting it to the system-wide rake.

This is because hiding a binary that will cause nothing but harm is good thing - I spent at least an hour of my time trying to track down this issue :-)

@ghost ghost assigned mpapis Dec 7, 2011
@mpapis mpapis closed this as completed in 664095b Dec 9, 2011
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

2 participants