My understanding is that the "rails:freeze:gems" task copies the Rails
source into the application''s vendor directory. Which is why I find
the following error surprising and confusing, because the task should
not involve writing to system files or directories:
% rake rails:freeze:gems
(in /Users/tallen/apps/pnc)
Freezing to the gems for Rails 2.3.5
rm -rf vendor/rails
mkdir -p vendor/rails
cd vendor/rails
ERROR: While executing gem ... (Gem::FilePermissionError)
You don''t have write permissions into the /opt/local/lib/ruby/gems/
1.8 directory.
rm -rf vendor/rails
Why does the task want to write to that directory? The output was
identical with the --trace option.
Thomas
--
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
