You can specify a version with confug.gem and that will keep it from updating later. I still say you should use bundler. The problem with rake gems:install is that you usually need to have the gems installed already to run the rake task. Yes... It's as stupid as it sounds. Bundler just has you type "gem bundle" which will always consistently package the same gems (if you specify versions) into vendor/gems/ and will isolate the app from the system environment (also if you specify, which you should).
Martin / on my iPhone On Jan 27, 2010, at 16:33, Brandon Black <[email protected]> wrote: > As a separate, but somewhat related note... > > You guys should check out the dependencies gem that is used by Monk. > It presents a pretty good alternative to managing all your gems in the > traditional way. Monk is primarily for Sinatra based web applications > rather than a rails application, but you could probably create a rails > project skeleton if you wanted too and the dependencies gem makes > deploying your app with all its necessary gems extremely clean and > easy. > > Dependencies Gem > http://github.com/djanowski/dependencies > > Monk > http://www.monkrb.com > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
