I've an user account on the shared Debian system which has RubyGems 1.1.1 installed and that i can't make sure they are upgrade it, a minimum of right now.
I am attempting to use a new RubyGems installation in your area on my small home directory, following a instructions from RubyGems user guide chapter 3.2 Setting up RubyGems inside a User Directory.
To date, I acquired now latest RubyGems (1.8.10) installed at $HOME/rubygems and that i have fixed the next atmosphere variables:
- Jewel_The place to find $HOME/rubygems/gems
- Road to have $HOME/rubygems/bin before systemwide /usr/bin (which consists of that old jewel)
Path ought to be working OK, since which jewel results as $HOME/rubygems/bin/jewel.
Still, after i run jewel -v I recieve 1.1.1.
This most likely has something related to ruby require winding up somewhere-wide files of RubyGems, because the $HOME/rubygems/bin/jewel begins with
require 'rubygems' require 'rubygems/jewel_runner' require 'rubygems/exceptions'
What must i caused by get my local-installed-version 1.8.10 running?
I'm not sure if this is just what you would like. However the simplest way would most likely be to make use of rvm. https://rvm.beginrescueend.com/rvm/install/
With rvm you might have yourself contained ruby atmosphere in your house directory with precisely the tools that you'll require.