Thursday, 15 July 2010

ruby - How to change gem environment settings? -



ruby - <RubyGems> How to change gem environment settings? -

i installed rbenv , set ruby , gems. if run gem env got following:

rubygems environment: - rubygems version: 2.2.2 - ruby version: 2.1.0 (2013-12-25 patchlevel 0) [x86_64-darwin13.0] - installation directory: /users/myusername/tools/.rbenv/versions/2.1.0/lib/ruby/gems/2.1.0 - ruby executable: /users/myusername/tools/.rbenv/versions/2.1.0/bin/ruby - executable directory: /users/myusername/tools/.rbenv/versions/2.1.0/bin - spec cache directory: /users/myusername/.gem/specs - rubygems platforms: - ruby - x86_64-darwin-13 - gem paths: - /users/myusername/tools/.rbenv/versions/2.1.0/lib/ruby/gems/2.1.0 - /users/myusername/.gem/ruby/2.1.0 - gem configuration: - :update_sources => true - :verbose => true - :backtrace => false - :bulk_threshold => 1000 - remote sources: - https://rubygems.org/ - shell path: - /users/myusername/tools/.rbenv/versions/2.1.0/bin - /users/myusername/tools/.rbenv/libexec - /users/myusername/tools/.rbenv/plugins/ruby-build/bin - /opt/local/bin - /opt/local/sbin - /users/myusername/tools/.rbenv/shims - /usr/bin - /bin - /usr/sbin - /sbin - /usr/local/bin - /users/myusername/tools/./bin - /users/myusername/tools/.rbenv/bin

well.. looks except spec cache directory , gem paths, others have self-configured paths. (so don't want dev-related directories straight placed in user home folder.) there way flexibly alter these 2 env variables without affecting normal functioning of ruby, gem , rbenv etc.?

thanks!

actually searched online , found solution.

just set next in .profile (max os) or .bashrc (linux)

export gem_path=/users/myusername/tools/.rbenv/versions/2.1.0/lib/ruby/gems/2.1.0 export gem_spec_cache=/users/myusername/tools/.rbenv/versions/2.1.0/lib/ruby/gems/specs

make sure folder set there existed. source .profile or .bashrc, or restart terminal. tested working env correct.

reference: https://github.com/rubygems/rubygems/pull/489

ruby gem environment

No comments:

Post a Comment