This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: native symlink
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- To: cygwin-developers at cygwin dot com
- Date: Mon, 13 May 2013 16:54:37 -0400
- Subject: Re: native symlink
- References: <515BB10C dot 9080101 at openafs dot org> <20130403152907 dot GD2468 at calimero dot vinschen dot de> <20130424103450 dot GM26397 at calimero dot vinschen dot de> <5177CABF dot 8040406 at openafs dot org> <20130424125043 dot GA18673 at calimero dot vinschen dot de> <51781CA4 dot 3040103 at openafs dot org> <20130424181412 dot GB26397 at calimero dot vinschen dot de> <3B3671F5-EBFE-480B-B592-90BA2270BDA6 at mac dot com> <20130513150015 dot GA20319 at calimero dot vinschen dot de> <519102F7 dot 3030804 at cwilson dot fastmail dot fm> <20130513153943 dot GD8890 at calimero dot vinschen dot de>
On 5/13/2013 11:39 AM, Corinna Vinschen wrote:
On May 13 11:12, Charles Wilson wrote:
Well, if the he wants to convert to a *native* link, then he'd use
winln(1) from cygutils rather than ln(1).
Why? What speaks against
#!/bin/bash
tgt=$(readlink "$1")
rm "$1" && CYGWIN=winsymlinks:native ln -s "${tgt}" "$1"
Oh, I forgot about the CYGWIN setting; I thought that the cygwin
"support" for native windows symlinks was just that it could now read
them and understand what they were (instead of being fooled
transparently by the underlying filesystem) -- and that Daniel's winln
program, contributed to cygutils, was the way to create them from user
space.
Now that I engaged the brain, that really doesn't make much sense, does it?
Right, 'CYGWIN=winsymlinks:native ln -s' would work fine. Sorry for the
noise.
--
Chuck