views:

7

answers:

0

It seems that both methods can freeze a gem into the vendor directory, but rake gems:unpack requires the gem to be listed in config/environment.rb as config.gem '<name of the gem>' before the rake is done.

On the other hand, rake gems:freeze requires installing the gem gemsonrails first, and uses the syntax rake gems:freeze GEM=haml and it doesn't require listing the gem in environment.rb first. But it doesn't work with the current GEM class (probably requires gem 1.3.6 instead of 1.3.7).

Besides these, what are the differences between them? Do they work very similarly and achieve the same purpose? gemsonrails's webpage wasn't updated since 2007; is rake gems:unpack the more preferred way of freezing a gem if not using Bundler?