[rspec-users] using config.gem to freeze rspec (not #577)

jacobhenry jachenry at gmail.com
Fri Oct 24 22:45:21 EDT 2008

We have a project running on edge rails that has rspec and rspec-rails 1.1.9
frozen in vendor/gems.  To freeze the gems we added two lines of code to

config.gem 'rspec-rails', :lib => 'spec/rails', :version => '1.1.9'
config.gem 'rspec', :lib => 'spec', :version => '1.1.9'

and then ran:

rake gems:install
rake gems:unpack
rake gems:unpack:dependencies
rake gems:build

The main goal is to freeze all common gems into the project so the
production server can simply run 'rake gems:build' and not worry about
installing anything.  This method of deployment is causing me to receive the
following error on my production machine whenever I run rake: 

rake aborted!
no such file to load -- spec/rake/spectask
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require'

I can see that spectask.rb exists in vendor/gems/rspec-1.1.9/lib/spec/rake/. 
Running 'script/generate rspec' did not solve my problem.  
View this message in context: http://www.nabble.com/using-config.gem-to-freeze-rspec-%28not--577%29-tp20118125p20118125.html
Sent from the rspec-users mailing list archive at Nabble.com.

More information about the rspec-users mailing list