Ilan Berci said the following on 15/02/08 02:10 PM:
In addition to Roger's suggestion, once you get it working, running:
should more properly safeguard you against server changes in the future
$ rake rails:freeze:gems
/home/antonaylward/bin/rake:9:in `require': no such file to load --
is obsolete. Use gem instead.
But I Still get
[ralphie]$ rake rails:freeze:gems
/usr/bin/rake:17:Warning: require_gem is obsolete. Use gem instead.
Does this mean that the system 'rake' is out of date?
The freeze seemed to settle on Rails-2.02
I don't think Typo likes that!
How would I freeze the gems to an earlier version?
After unfreezing the above I listed the gems to see which version of
rails there were. Only 2.02 and 1.2.6, so I tried
[ralphie]$ rake rails:freeze:edge TAG=rel_1.2.6
which now results in
./public/../config/boot.rb:16:in `require': no such file to load --
from ./public/../config/environment.rb:8:in `require'
from ./public/dispatch.fcgi:21:in `require'