ruby - Why does RVM install duplicate gems for different gemsets? -


so, i've created separate rvm gemset each of rails projects. both use same version of ruby 1.9.3.

this causes bundle install install fresh set of gems both projects. doesn't matter if other project has exact same version of gem installed in other gemset. i'm guessing expected behavior me seems inefficient use of hard drive space , bandwidth.

i know manually move of gems global gemset, seems tedious me , prone breaking if dependencies change particular project.

is there better way organize things, or have rvm auto detect when gem version installed , use copy?

or there better alternative rvm should using.

this design. gemsets allow isolate libraries used don't have accidental interaction between projects. if don't need isolate can use interpreter without gemset:

rvm use 1.9.3 

if there few gems use across projects, switch global gemset interpreter:

rvm use 1.9.3@global 

gem install common gems , won't re-installed per-project anymore when in gemset.

while gemsets aren't efficient in terms of bandwidth or hd space, extremely handy because can blow away dependencies project , re-bundle scratch time want to. eliminate accidentally changing versions of dependencies. if don't gemsets, correctly specifying versions in gemfile can pretty far on without them.

as far alternatives, rbenv main 1 i'd check out.


Comments

Popular posts from this blog

java - Play! framework 2.0: How to display multiple image? -

gmail - Is there any documentation for read-only access to the Google Contacts API? -

php - Controller/JToolBar not working in Joomla 2.5 -