rvm - Should I check in `.ruby-gemset` and/or `.ruby-version`? -


i've updated rvm, , in place of old .rvmrc, auto-created .ruby-gemset , .ruby-version.

i've had .rvmrc files contents rvm use --create default@project_name. however, .ruby-version contains specific ruby version i'm running rather default. i'm hesitant check in.

also, heard on podcast 1 shouldn't check in .ruby-gemset because others may have own preferences how name gemsets.

when should or shouldn't check in .ruby-gemset and/or .ruby-version?

specifically:

  • what of tradeoffs?
  • how type of project affect decision (for example, applications vs gems)?
  • if should checked in, how type of project affect should go in these files?

citations from creators of tools rvm, rbenv, etc appreciated in answer.

for standard projects

check in .ruby-version if project depends on ruby ruby-2.0.0. check in .ruby-gemset if team agreed on it. add .rvmrc .gitignore can override .ruby-* files settings .rvmrc.

for gems

check in .ruby-version ruby-1.8.7 if project still targets ruby 1.8.7, otherwise check in if gem requires it. not check in .ruby-gemset.


Comments

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

keyboard - Smiles and long press feature in Android -

node.js - Bad Request - node js ajax post -