Question

I’m working on a project that runs on Rails ~> 3.0 on the master branch, and ~> 3.1 on another branch.

Obviously those 2 branches need different gemsets.

Do you know of a convenient way of handling the situation using RVM?

I’ve thought of a couple options, none of them optimal:

• using gemsets I would have to remember to manually switch gemset after each git checkout

• using bundle package I would have to track the vendor/bundle directory

• a mix of the two approaches is not even possible, since .bundle/config is not tracked

• I could write a git post-checkout hook, but it sounds a bit hacky (hardcoded branch names and all that)

Is there a better way that I’m failing to think of?

Answer 1

I ended up using the following git post-checkout script.
In the master branch, I was using gems installed in $GEM_HOME. In the other branches, gems were installed locally to vendor/cache.

#!/usr/bin/env bash

#set -x

git_rev() {
  ref=$(git symbolic-ref HEAD 2>/dev/null) || return
  echo ${ref#refs/heads/}
}

ref=$(git_rev)

case $ref in
  master)
    echo "removing .bundle/config"
    mv .bundle/config .bundle/config.no
    ;;
  *)
    if [ -f .bundle/config.no ] ; then
      echo "using vendor/cache"
      mv .bundle/config.no .bundle/config
    fi
    ;;
esac