[darcs-users] 1.0.8 / 1.0.6 interop errors?

[Esa Ilari Vuokko]

On 7/9/06, David Roundy <droundy at darcs.net> wrote:
> On Thu, Jul 06, 2006 at 07:43:18PM +0200, Eric Y. Kow wrote:
> > On Wed, Jul 05, 2006 at 10:40:34 -0700, Zooko O'Whielacronx wrote:

> > > It would be great if Windows users could use openssh, but I thought that
> > > darcs invoked ssh with putty-specific command-line format.
> >
> > Looking at the code, I do not believe this to be the case; all we do
> > is look for the environment variable DARCS_SSH.  There is no Windows
> > specific stuff as far as I can see.  OpenSSH on Windows should be OK.
>
> I believe the trouble is that OpenSSH on Windows (at least the cygwin
> version) won't accept windows absolute path names.  We might be able
> to alleviate this by always using relative path names, but that's a
> bit scary when we use unsafeInterleaveIO.  I suppose we could wrap the
> ssh call in a withWorkingDir (or whatever it's called) to clean that
> up, but it's still a bit of a hack.  On the third hand, it would be
> great for users to be able to use openssh on windows.  And keep in
> mind, I might be remembering this all wrong.  The trouble is that
> cygwin ssh thinks the drive letter corresponds to a server named "c".

I don't have a cygwin at hand, but yes.  This is the problem, cygwin uses
something like /cygdrive/c/foo for c:\foo.  Why not give up and add
commandline option(s) to darcs to invoke cygwin-openssh vs putty
behaviour?  I think darcs also doesn't allow putty sessions to be
used, and if we had option, we could invent syntax for that.

How about --enable-workaround=foo and --disable-workaround=foo?

Best regards,
--Esa