DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=bRXO
	rjSoKiw6wz/JYb5x8wBpa4FJU4tTL9YmiJ1G0KEsQr6dQ/J0H1UK5FR4NYY2gDkg
	0U8zl4Ke59oW46YhKO/MxX/XvrZVoh4dmgsp/w9fmePO8m7EtDj9jdZFx6CtdpyK
	n20GfF+hSJEX85kwbb+ketTb8nFXGGdnl4Urp1Y=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Thu, 14 Aug 2014 17:44:31 +0100
From: Adam Dinwoodie <adam AT dinwoodie DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: repo with CYGWIN=winsymlinks:nativestrict
Message-ID: <20140814164431.GA27917@dinwoodie.org>
References: <53EC9FB9 DOT 8090100 AT realsil DOT com DOT cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <53EC9FB9.8090100@realsil.com.cn>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Thu, Aug 14, 2014 at 07:38:33PM +0800, Robert Bu wrote:
> If I set CYGWIN=winsymlinks:lnk, repo works. However, Windows native
> Git tool, such as TortoiseGit cannot read the symlink file. I think
> it treats the symlink file as a normal file and tries to parse the
> file format as Git specifies.

I've never used native Windows Git tools, but if they work in a similar
way to Windows Subversion tools, they're expecting a "symlink" to be
something that doesn't act like a symlink in any way whatsoever.

I suspect this is one of those areas where Cygwin and native-Windows
tools aren't going to play nicely without a lot of difficulty because of
the fundamental differences between *nix and Windows approaches.

The only useful suggestion I have is to abandon Windows Git tools.  If
you want GUIs you could try gitk and git-gui in Cygwin (you'll need to
install an X server to use these).

You could also try suggesting the TortoiseGit folk handle the symlinks
created by Cygwin (of whatever flavour) as symlinks in the Git
repository, but even if they accept that as a feature request I'd guess
it'd be a while before it'd be available.

> I guess Windows native tool can handle the symlink if
> "CYGWIN=winsymlinks:nativestrict".
> However, if I set CYGWIN=winsymlinks:nativestrict, repo init fails with
>     os.symlink(os.path.relpath(src, os.path.dirname(dst)), dst)
>     OSError: [Errno 2] No such file or directory

This seems odd, although the error here really doesn't say very much
about what's going on.  I've no idea if this is being run in Cygwin
Python or Windows Python, and I have no idea of the directory structure
and symlink locations in the paths it's using.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple