What I'm actually looking to do is programatically ensure within a Rakefile that a specific gem version is installed in the user's gems dir
I can do this with shell code, just hoped that I could do it a bit more efficiently directly using Gem in Ruby
going a little further down the rabbit hole: OS X (still) ships with RubyGems 2.0.14. If I don't first update it to the latest with `gem update --system`, I can't do `Gem::Installer.new`, even though the Gem::Installer class seems to be present in the System's Ruby 2.0.0 dir within the rubygems lib.
I have a general Rake question: I'm working on a project with a very large Rakefile and it makes branching/merging problematic because many changes go into a single file. I was looking at splitting it up using simply the "rakelib/foo.rake" pattern. Does this method have any disadvantages for simply splitting up our tasks into files more logically?