I'd say rather than install the same versions of the various components the book used, stick with what you have now and just remember if something looks different (eg. the migration file naming) or is broken, that it
Watch Your Version Numbers!
It’s possible that by the time you read this, a more recent version of Ruby, SQLite, or one of the other packages mentioned here will have been released. Beware! Don’t just assume that because a package is newer, it can reliably be used for Rails development. While, in theory, every version should be compatible and these instructions should still apply, sometimes the latest is not the greatest.
In fact, the Rails framework itself also has a reputation for experiencing large changes between releases, such as specific methods or attributes being deprecated. While every effort has been made to ensure the code in this book is future-proof, there’s no guarantee that changes included in future major releases of Rails won’t require this code to be modified in some way for it to work. Such is the fast-paced world of web development!
Time Flies The version of Instant Rails used to test the code in this book was 2.0. As discussed earlier in the chapter, due to the fast-changing nature of the framework, I can’t guarantee that later versions will work.