Thanks Jamis. On 19/09/2007, at 2:50 AM, Jamis Buck wrote:
> I'm *this* close to putting the --password option back in, and to heck > with security concerns. Pulling that option has opened a can of worms. > :( > > Unfortunately, handling local command streams similarly to remote > streams is non-trivial, mostly because of Windows. If someone wants to > take a stab at it, I'll consider a patch, but right now, it is likely > that cap 2.1 will use the --password option to specify the password > for subversion. My use case is that I don't want the remote server having my SVN auth details which has write access to a bunch of repositories. I'm using the :scm_username and :scm_password to specify a read-only user for the remote server. I'd be happy using the current solution for remote streams only, and using auth cache locally (ignoring :scm_username and :scm_password). How about simply removing #authentication from the #query_revision svn command args? The following fix works well for me: http://pastie.caboo.se/99681 If you still needed the flexibility of specifying local auth details maybe you could have #query_revision use a #local_authentication which drew from two local-only vars: :scm_local_username and :scm_local_password ? -- tim --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
