[darcs-users] 1.0.8 / 1.0.6 interop errors?

Zooko O'Whielacronx zooko at zooko.com
Wed Jul 5 17:40:34 UTC 2006

Eric Y. Kow wrote:
> 3) I'd rather not disable CM functionality for Windows, because that
>    would deprive OpenSSH users under Win of their CM.  Perhaps we
>    could detect that the ssh in question is putty and if so, assume
>    we don't have CM capability.

It would be great if Windows users could use openssh, but I thought that 
darcs invoked ssh with putty-specific command-line format.


I haven't yet confirmed this.

If it is true as per issue29 that darcs detects that it is running on 
Windows and passes different command-line format to "ssh", then that 
raises the question of why darcs requires putty ssh to be renamed from 
"plink.exe" to "ssh.exe".


This offers a possible path forward: darcs could check for the existence 
of "ssh", and if present assume that it is openssh and use the openssh 
command-line.  Failing that, darcs could check for the presence of 
"plink" and if present use the putty command-line.

I guess it would be complicated by the fact that scp.exe could be either 
openssh or putty.

> 4) It is expected that darcs create a darcs-ssh directory somewhere
>    under the tmp directory.  What would not be normal is if the
>    directory was being created somewhere else.

I've seen a darcs-ssh directory created in the root of my repository 
i.e. in among my own source code files rather than in some kind of temp 



More information about the darcs-users mailing list