…install gems into ~/.gem/$ruby/$version. chruby only modifies $PATH, $and $ GEM PATH, and does not hook cd or rely on shims.
Ruby on at Top [ , California]
RoR Developer, Platform at [ , Washington]
Software - Experienced/Senior at Intent Media [ , York]
…caches them . Sometimes bundler must modify your and GEM PATH environment variables. These environment variables tell rubygems where to locate gems on your file system. Unfortunately, if these variables are modified after the specification cache is built, that means the cache must be cleared. Until recently, bundler always cleared the rubygems cache . Since rubygems can load gemspecs before bundler gets activated (or may even while bundler is being activated!), …
…setting gem home or gem path via gemrc as a critical feature. Setting theand GEM PATH environment variables will work just as well. Removing the feature also allows to avoid loading for default operations as the gemrc file is in YAML format.
(by changing GEM PATH and GEM HOME and then telling rubygems about the change)
- raising an exception if it's for a different ruby installation. This switch makes it
possibly to dynamically switch your ruby applications gemset whilst running.
Of course, dealing with a direct port of the API isn't always nice when you're writing a lot of code
env.alias_list feels clunky compared to most ruby code and some of the tools are rough around the
edges. With this in mind, …
…directory for the given gemset (ensuring gems are installed in the correct place) but it also sets GEM PATH .
Much like PATH , GEM PATH is a colon separated list of directories that rubygems uses to look up gems when requiring them. By installing a gem to the global gemset for any ruby, e.g. ree-1.8.7-2010.02@global , it will automatically be made available (including it's binaries) inside both the default gemset and any user-defined gemsets. E.g.,
Some people find that their app cannot load a certain library when the app is started in Phusion passenger, but can when the app is started with e.g. Mongrel or Thin. This is almost always caused by some environment variable that's set in the shell but not in the web server: everything you set in /etc/bashrc and friends don't have effect on processes started from the web server. …
, GEM PATH and are unset before running the installer so that those options can't interfere with installation.
RUBY HEAP SLOTS GROWTH FACTOR wasn't properly parsed as a floating point number. This has now been fixed.
Fixed REE issue #39. More packages We now provide packages for:compilation problems. Patch contributed by firstname.lastname@example.org.
Ubuntu 10.04 32-bit
Ubuntu 10.04 64-bit…
…just too tired at the moment.
interesting, but the bug seems to be possibly 2 things: emptyshould not be used, and when the join occurs I think it is creating an invalid GEM PATH=":/ Users/User/.gem/ruby/1.8:/opt/local/lib/ruby/gems/1.8:" ... it should not have that leading ':'