You can set :copy_cache to be the name of the cache directory to use. Setting it to be the name of the branch seems like a good idea, but too specific to subversion to put in cap itself, I think.
- Jamis Paul Dowman wrote: > Hi, I think there's a small bug with the new :copy_cache setting with > svn. If you change the branch in your deploy.rb (I deploy either the > trunk or a release branch) the cached version doesn't switch to the > new location, and you deploy the wrong branch without any warning. > > I think the issue is that Subversion#sync only (subversion.rb:30) only > uses revision and destination, it assumes that repository hasn't > changed. > > If it's going to use the same cache dir it would need to do an svn > switch, but an easier way to solve it might be to use a different > cache dir, i.e. use the branch in the cache's dir name. If copy_cache > in copy.rb changed depending on the svn branch there would be no > problem. > > I'm using version 2.3.0. > > Paul > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
