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 received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/3f6ecb20-05a6-4024-8791-f9cffac54255%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Carlos Mathiasen
2013-Sep-02 14:36 UTC
Re: how to handle two different gem version using RVM
You can use gemset for that[0] [0] https://rvm.io/gemsets Matt''s On Mon, Sep 2, 2013 at 10:34 AM, honey ruby <emailtohoneyruby-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>wrote:> 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 received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To view this discussion on the web visit > https://groups.google.com/d/msgid/rubyonrails-talk/3f6ecb20-05a6-4024-8791-f9cffac54255%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CALX-aHoOzrNe4xG6h3%3D20EDaCPcrTrQ%3DWjzCHdhTA%2B%3D_5_QcUw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
On 2 September 2013 15:36, Carlos Mathiasen <gunmath987-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> You can use gemset for that[0] > > [0] https://rvm.io/gemsetsAlternatively 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> > Matt''s > > > On Mon, Sep 2, 2013 at 10:34 AM, honey ruby <emailtohoneyruby-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > wrote: >> >> 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 received this message because you are subscribed to the Google Groups >> "Ruby on Rails: Talk" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org >> To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/rubyonrails-talk/3f6ecb20-05a6-4024-8791-f9cffac54255%40googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To view this discussion on the web visit > https://groups.google.com/d/msgid/rubyonrails-talk/CALX-aHoOzrNe4xG6h3%3D20EDaCPcrTrQ%3DWjzCHdhTA%2B%3D_5_QcUw%40mail.gmail.com. > > For more options, visit https://groups.google.com/groups/opt_out.-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLvHZO5OJbzD0zv7rbNd1y9Fc5jmKt7EBXtnKEubX9xqiw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
On Mon, Sep 2, 2013 at 10:34 AM, honey ruby <emailtohoneyruby-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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 Aronson, 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/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAHxKQiif-sMRfbQiYwB7kqwOkbd9q3SbqH0-zh2YQb3MfpORgg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Jordon Bedwell
2013-Sep-02 15:28 UTC
Re: how to handle two different gem version using RVM
On Mon, Sep 2, 2013 at 10:23 AM, Dave Aronson <googlegroups2dave-BRiZGj7G2yRXqviUI+FSNg@public.gmane.org> wrote:> On Mon, Sep 2, 2013 at 10:34 AM, honey ruby <emailtohoneyruby-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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.You can also kick on global caching in RVM and use Gemsets too if you prefer to keep things at a "global" level. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAM5XQnzAs7HRFt6bQ18nkMHZ9ydPgX7fJO728RDzHwmkYMqvhw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.