Wrestling with the VFS tar baby, mostly for TORQUE-174.
Wrestling with the VFS tar baby, mostly for TORQUE-174.

When the cache option of javascript_include_tag is used, Rails will
attempt to write files beneath public/javascripts, expecting various
File class methods to work, e.g. rename, chown, chmod, and utime.
Further, it writes temporary files in order to grab a File::Stat
object to use for setting mode and owner, so our VFS::File::Stat with
its hard-coded platform specific mode wasn't cutting it (it generated
a file that wasn't readable on OSX).  Clever of Rails, but sucky for
VFS.

Because I adapted Ben's chmod() idiom for chown() and utime(), I
factored the idiom out into writable_operation().

I think I have TORQUE-174 fixed for 'sploded apps, but I'm not sure
what to do about archives.  Still need to add some test cases for this
stuff, too, now that we know what it's supposed to do.  ;)

torquebox/torquebox-release,mje113/torquebox,samwgoldman/torquebox,torquebox/torquebox,mje113/torquebox,vaskoz/torquebox,vaskoz/torquebox,vaskoz/torquebox,ksw2599/torquebox,torquebox/torquebox-release,torquebox/torquebox-release,torquebox/torquebox,samwgoldman/torquebox,vaskoz/torquebox,mje113/torquebox,samwgoldman/torquebox,ksw2599/torquebox,samwgoldman/torquebox,torquebox/torquebox-release,ksw2599/torquebox,torquebox/torquebox,ksw2599/torquebox,torquebox/torquebox,mje113/torquebox