From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Forcing setup.exe not to create WSL symlinks
Date: Wed, 26 Aug 2020 20:29:19 +0200 [thread overview]
Message-ID: <875z95tg5c.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAALQ5rnxo0_pJqTo5+617sZ6NPyDEuw5LkK_w5tMihYnTRfHrg@mail.gmail.com> (Michael Wild via Cygwin's message of "Wed, 26 Aug 2020 14:14:01 +0200")
Michael Wild via Cygwin writes:
> Is there a way to disable WSL symlinks when installing Cygwin with
> setup.exe? Problem is that Docker on Windows apparently doesn't support
> them (see https://github.com/moby/moby/issues/41058). I would like to use a
> custom Docker image for GitHub Actions to reproducibly build my packages
> but am failing to build the base image because of this.
That description is not very clear. If the symlinks are created during
postinstall, then they should obey the value of CYGWIN environment that
is in effect at that time. If so, then the behaviour should start
appearing with cygwin-3.1.5, which is the first release that has the
code supporting these (and makes them the default). I'm not aware that
the behaviour of setup.exe has changed in that respect recently, but I
haven't checked thoroughly.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2020-08-26 18:29 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 [this message]
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
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=875z95tg5c.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/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).