From: Michael Wild <themiwi@gmail.com>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Forcing setup.exe not to create WSL symlinks
Date: Mon, 31 Aug 2020 06:51:23 +0200 [thread overview]
Message-ID: <CAALQ5r=NegZG8NAnKe9yX8s6kyakcox7vS444UC7qmP20DyQMQ@mail.gmail.com> (raw)
In-Reply-To: <8249305f-d6f8-48bd-5201-02e778e0193e@dronecode.org.uk>
On Sun, 30 Aug 2020, 22:24 Jon Turney wrote:
> On 27/08/2020 06:48, Michael Wild via Cygwin wrote:
> > On Wed, Aug 26, 2020 at 10:57 PM Jon Turney wrote:
> >>
> >> However, even if that's fixed, there's no value for winsymlinks in
> >> CYGWIN env var to specify the behaviour of Cygwin 3.1.4 and previous
> >> (i.e. always create traditional symlinks, don't use WSL symlink reparse
> >> points)
> >
> > Thanks Jon for the elaboration. Isn't winsymlinks=lnk supposed to do this
> > per the documentation?
>
> No.
>
> I'm not sure what documentation you are looking at, but [1][2] seems
> reasonably clear that the behaviour of Cygwin 3.1.4 and earlier (what I
> referred to as "traditional cygwin symlinks") isn't the same as ".lnk
> symlinks".
>
> [1] https://cygwin.com/cygwin-ug-net/using.html#pathnames-symlinks
> [2] https://cygwin.com/cygwin-ug-net/using-cygwinenv.html
Ah, I was jumping ahead there. My intention was having no WSL symlink
reparse points. And per my experiments, winsymlinks:lnk gets that job done.
Michael
prev parent reply other threads:[~2020-08-31 4:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 12:14 Michael Wild
2020-08-26 15:19 ` Andrey Repin
2020-08-26 15:24 ` Michael Wild
2020-08-26 18:29 ` Achim Gratz
2020-08-26 19:06 ` Michael Wild
2020-08-26 20:15 ` Michael Wild
2020-08-26 20:55 ` Jon Turney
2020-08-27 5:48 ` Michael Wild
2020-08-27 9:00 ` Corinna Vinschen
2020-08-27 9:38 ` Andrey Repin
2020-08-27 9:44 ` Michael Wild
2020-08-27 12:48 ` Michael Wild
2020-08-27 12:49 ` Michael Wild
2020-08-30 20:24 ` Jon Turney
2020-09-06 14:44 ` Jon Turney
2020-08-30 20:24 ` Jon Turney
2020-08-31 4:51 ` Michael Wild [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAALQ5r=NegZG8NAnKe9yX8s6kyakcox7vS444UC7qmP20DyQMQ@mail.gmail.com' \
--to=themiwi@gmail.com \
--cc=cygwin@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).