From: Gene Pavlovsky <gene.pavlovsky@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Native symlinks and setup.exe
Date: Sun, 02 Oct 2016 23:35:00 -0000 [thread overview]
Message-ID: <CAPTiy3NY7oB0g4fg_nmsF8YzzPRdMh2aFnezy5ceoKiM8UWW8w@mail.gmail.com> (raw)
In-Reply-To: <nsqpd6$tvm$2@blaine.gmane.org>
Thorsten,
That's a great pointer. I've just investigated using the `flex`
package as an example.
Untarring flex-2.6.1-1.tar.xz, usr/bin/flex++ is extracted as a Cygwin
symlink to usr/bin/flex.exe.
If I create a native symlink to flex.exe, tar it all up to a new tar
archive, then extract it somewhere else, the native symlink is
extracted as native, as expected.
So, when installing, the type of symlinks doesn't honor the CYGWIN
option since they are just unpacked by tar as is.
The question I'm proposing now - should `tar` be modified to honor the
CYGWIN option and automatically convert symlinks when extracting, if
necessary?
--Gene
On 2 October 2016 at 14:00, Thorsten Kampe <thorsten@thorstenkampe.de> wrote:
> * Gene Pavlovsky (Sat, 1 Oct 2016 18:52:47 +0300)
>>
>> I'm installing Cygwin 64-bit on a fresh Win 7 x64 installation.
>> 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?
>
> Setup does not create symlinks. That's either done by the postinstall
> scripts or the contents of the package are simply unpacked to the
> folder. So the answer to your question is: the symlinks are not
> created but copied, that's why.
>
> Thorsten
>
>
> --
> 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
>
--
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-02 21:47 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
2016-10-02 11:48 ` Thorsten Kampe
2016-10-02 23:35 ` Gene Pavlovsky [this message]
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=CAPTiy3NY7oB0g4fg_nmsF8YzzPRdMh2aFnezy5ceoKiM8UWW8w@mail.gmail.com \
--to=gene.pavlovsky@gmail.com \
--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).