How to handle two different gem version using RVM

Hi Everyone,

I have two projects one projects need gem version of 1.3.7 and another
one
1.4.2 using RVM can we have two different gem versions.

Thanks in advance

You can use gemset for that[0]

[0] RVM: Ruby Version Manager - RVM Gemsets

Matt’s

On 2 September 2013 15:36, Carlos M. [email protected]
wrote:

You can use gemset for that[0]

[0] RVM: Ruby Version Manager - RVM Gemsets

Alternatively if you specify the version you want in Gemfile and then
run bundle install it will use that version for that application.
Repeat for the other application.

Colin

On Mon, Sep 2, 2013 at 10:23 AM, Dave A.
[email protected] wrote:

separated for minimal interference, and make it much easier for you to
navigate to the source of a given gem if you ever need to see it. You
can do this with or without rvm, or any other Ruby-version manager.

You can also kick on global caching in RVM and use Gemsets too if you
prefer to keep things at a “global” level.

On Mon, Sep 2, 2013 at 10:34 AM, honey ruby [email protected]
wrote:

I have two projects one projects need gem version of 1.3.7 and another one
1.4.2 using RVM can we have two different gem versions.

Also consider vendoring your gems. I’m not sure how to migrate an
extant project to use this technique, but when you create a project,
do “rails new project_name --skip-bundle”, cd into the project, and do
“bundle install --path vendor --binstubs”. Then all the gems will be
down under the vendor dir. This will keep your projects well
separated for minimal interference, and make it much easier for you to
navigate to the source of a given gem if you ever need to see it. You
can do this with or without rvm, or any other Ruby-version manager.

-Dave


Dave A., the T. Rex of Codosaurus LLC,
secret-cleared freelance software developer
taking contracts in or near NoVa or remote.
See information at http://www.Codosaur.us/.