Remove sudo from gem installation instructions #66
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tmm1
added a commit
that referenced
this pull request
May 4, 2013
Remove sudo from gem installation instructions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Is there any good reason to be recommending users install with sudo?
Everything seems to work sans sudo, and since gems can execute arbitrary code, installing with sudo can get dangerous if anyone manages to hijack this gem or one if it's dependencies on RubyGems.
If a user wants to install with sudo, they certainly can, and then they are assuming all the risk by being explicit. I don't think that we should be actively recommending it.