Updating ruby gem

If you're on mac OS, we recommend installing rbenv with Homebrew.

Ruby Gems is very rich, and probably one of the most mature package management applications that exists.

It provides the developers a standard structure, along with a standard format to deal with application collections (packages) called Gems.

With rbenv and Bundler binstubs you'll never again need to in a cron job or Chef recipe to ensure you've selected the right runtime.

The Ruby version dependency lives in one place—your app—so upgrades and rollbacks are atomic, even when you switch versions. rbenv is concerned solely with switching Ruby versions. A rich plugin ecosystem lets you tailor it to suit your needs. Once rbenv has determined which version of Ruby your application has specified, it passes the command along to the corresponding Ruby installation.

As we have mentioned previously, a Gem is a package that contains different sets of components.

Each Gem has a version and a basic definition of the platform it was built for.

They can (and usually do) come with additional files to give information about the package, and despite the importance, only sometimes with a decent usage manual.

Once the package manager installs a package, all these elements become accessible inside the environment they are set (e.g. and helps you with many things from downloading to packaging and distributing Ruby applications -- and of course, relevant binaries and libraries.

Compile your own Ruby versions, or use the ruby-build plugin to automate the process. Each Ruby version is installed into its own directory under with RVM.

Tags: , ,