-
Notifications
You must be signed in to change notification settings - Fork 31
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
ignoring ~/.gemrc options #24
Comments
Interesting. Thanks for using I wonder if gem-install does a lookup to check whether it's running under sudo and then reaches back for the user's What's the result of your gemrc being ignored? Is it settings such as |
My
What's happening is that the scripts are being installed into |
yikes is there even a work around? Can it even know who the calling user On Sat, Aug 30, 2014 at 4:44 AM, John Purnell [email protected]
|
The global file is unfortunately system dependant:
I don't know how rubygems is getting the correct
the correct user id is returned. |
Same issue here. ---
gem: --no-document and it seems to always builds docs. |
specific_install 0.2.11, ruby 2.0.0, os x 10.9.4:
When installing with say
sudo gem specific_install -l https://github.com/hisashim/docdiff.git
the options specified in the~/.gemrc
are ignored. But when usingsudo gem install docdiff
the options in~/.gemrc
are applied.The text was updated successfully, but these errors were encountered: