From: Herbert Stocker <hersto@gmx.de>
To: cygwin@cygwin.com
Subject: Re: Native symlinks and setup.exe
Date: Sun, 02 Oct 2016 06:27:00 -0000 [thread overview]
Message-ID: <57F03ADA.8060406@gmx.de> (raw)
In-Reply-To: <6b81e0d4-f9ac-a997-54f7-4c30347b61f3@gmail.com>
On 01.10.2016 23:32, Vlado wrote:
> On 1.10.2016 17:52, Gene Pavlovsky wrote:
>> Before running setup.exe I've set the system env var
>> CYGWIN=winsymlinks:native
>> After that I ran setup-x86_64.exe and installed cygwin64.
>> The symlinks to .exe files in bin, created by setup, are not native
>> symlinks, they are cygwin symlinks. Apparently, setup doesn't honor
>> the winsymlinks:native CYGWIN option. Is that intended (why?) or a
>> bug?
>
> Hi Gene,
>
> IMHO CYGWIN variable controls Cygwin behavior, but setup is native
> Windows app.
> What You are describing is expected behavior.
From a sole technical point of view, it's maybe expected.
But from a software usage point of view not:
Gene wants to use Cygwin with native links.
And setup.exe is part of Cygwin. Therefore setup.exe *should* honor
the CYGWIN variable.
(those parts of CYGWIN that make sense for the setup).
Or formulated another way:
Gene wants to use native links with Cygwin. Cygwin does have that
capability. How should he instruct setup.exe to do so?
Herbert
--
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
next prev parent reply other threads:[~2016-10-01 22:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 18:49 Gene Pavlovsky
2016-10-01 21:56 ` Vlado
2016-10-02 6:27 ` Herbert Stocker [this message]
2016-10-02 11:48 ` Thorsten Kampe
2016-10-02 23:35 ` Gene Pavlovsky
2016-10-03 18:26 ` Thorsten Kampe
2016-10-04 6:57 ` Gene Pavlovsky
2016-10-04 8:15 ` Vlado
2016-10-04 20:42 ` Gene Pavlovsky
2016-10-04 19:21 ` Gerrit Haase
2016-10-04 20:54 ` Gene Pavlovsky
2016-10-04 21:04 ` Vince Rice
2016-10-04 21:20 ` Eric Blake
2016-10-04 23:15 ` Gene Pavlovsky
2016-10-05 3:03 ` Gene Pavlovsky
2016-10-04 19:39 ` Linda Walsh
2016-10-02 20:08 ` Andrey Repin
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=57F03ADA.8060406@gmx.de \
--to=hersto@gmx.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).