public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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: Thu, 27 Aug 2020 07:48:36 +0200	[thread overview]
Message-ID: <CAALQ5rnsexseL=gNd5VKkZSi2=Feg4vFLFGG8OmFcmVhyKvWoQ@mail.gmail.com> (raw)
In-Reply-To: <1f4a80f7-0e14-1641-3fce-317ac2a6dd00@dronecode.org.uk>

On Wed, Aug 26, 2020 at 10:57 PM Jon Turney wrote:

>
> It turns out to be the case that setup doesn't propagate the CYGWIN
> environment variable into the environment for scripts it runs, so
> setting that isn't going to make any difference.  That should probably
> be considered a bug.
>
> 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? Could Corinna be convinced to include an option
where this can be done? To be honest, my hopes are greater to get this
worked-around in a useful timeframe from the Cygwin side than getting the
proper fix into Docker.

Michael

  reply	other threads:[~2020-08-27  5:48 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 [this message]
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

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='CAALQ5rnsexseL=gNd5VKkZSi2=Feg4vFLFGG8OmFcmVhyKvWoQ@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).