Freeze_gems broke my app


#1

WinXP/ruby1.8.4/rails1.0. did a “rake freeze_gems” and got:


Freezing to the gems for Rails 1.0.0
rm -rf vendor/rails
mkdir -p vendor/rails
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
The system cannot find the path specified.
rake aborted!
undefined method `to_str’ for nil:NilClass

i’m assuming the errors occur b/c windows doesn’t know what to make of
the unix-
specific “rm” or the forward-slash path character. ok, that’s fine, i
can’t
freeze.

however, any subsequent invocation of rake gives me:


rake aborted!
no such file to load –
Z:/Tools/sandbox/config/…/vendor/rails/railties/lib/initializer
Z:/Tools/sandbox/rakefile:4

worse, i can no longer run webrick:


d:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in
require__': no such file to load -- ./script/../config/../vendor/rails/railties/lib/initializer (LoadError) from d:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:inrequire’
from ./script/…/config/boot.rb:13
from
d:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in
`require’
from script/server:2

yikes. so my questions, in order of importance:

  1. have i hosed my app beyond the point of repair?
  2. if the answer to [1] is no, is there a file i can edit to get me back
    to a
    state before the “bad time”?
  3. does freeze_gems work on win32 systems?

thanks!