X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=EzBkar0
	AHebJAUt+kOrdzi3r8xg/PUP/dIVUeW9Z8eNyrgf25mQ6ksWBq2EGOFLQQuOhcpA
	ZFlSjJB5dphukZXjVq9NIeFFtmzfvKI8R92bAATB2FkGb8M0IjMl1fpRpLX0MbrK
	H+l1gjUV8F6KKMZw6oKnkSKfMx1alClssius=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; s=default; bh=Cgrj6b9cwJGMI
	vo2dAaTlXe8CkM=; b=Bo9EJh61qO6gnNyucyz1Q71poY+73yXwL6gY/1a5/5628
	Bmu/JQuCb462/dXJl7PidQsODsZh4lwZ0/aXter8IrnaF5Twk6aeuIYQrSQu9vys
	SPc9vA6fg+sT2vXGOJQQ6b/L7fL+nIYQHOeduin/tlcZot5I8ZbkGHfoUM5f1o=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=ham version=3.3.2 spammy=kampe, Kampe, Thorsten, Hx-languages-length:1694
X-HELO: mail-it0-f43.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:mime-version:in-reply-to:references:from:date         :message-id:subject:to;        bh=O5emd0nsb9eGtSQ3ZNofftFBGeSegFasV2spVKvr96c=;        b=XbR0yFz0RZi0BKSXo2J94iZJJffDUT+fgb11A5+A1xrABlv2tmMbrK4P0xhihxyQ/O         /rvG28K1NMcOt+ml9M90bpyvvlS39fTYU7DSqVVG8PUIkO0kHt3X8uRNsYmpjwA7Aueu         nAg/w5hW1Xi4gy0O2s4ef4WLlbLGJ+luzenxxgIpsvHRYWn4Fwhj62PL9+dmsNUViYAz         0xZH9diA0y4tU4wrRaKYgJd4jCUcUaVUYmBzDBAGObb5aURe0YHHWctmEj50yKgBhdtA         jbXcjc2/uiEYcETwB/S6gkBke62eE8+1oU+z/PkMLqkaK+bNqWokedFyNr3TGz0O0OQj         J9Gw==
X-Gm-Message-State: AA6/9Rnq31WGrQd5H2wQwMvgFZMVJGgn+ltj7N+jV8nF8bQdUvhfxps0ePTOSfNgKvwWvPffc9zAyZdqhSLrEA==
X-Received: by 10.36.95.80 with SMTP id r77mr5161420itb.92.1475444814850; Sun, 02 Oct 2016 14:46:54 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <nsqpd6$tvm$2@blaine.gmane.org>
References: <CAPTiy3O9eEhdgWcdEKkY=Egd+_8WJtxOc6WXjhecr9Du=-f=fg AT mail DOT gmail DOT com> <nsqpd6$tvm$2 AT blaine DOT gmane DOT org>
From: Gene Pavlovsky <gene DOT pavlovsky AT gmail DOT com>
Date: Mon, 3 Oct 2016 00:46:54 +0300
Message-ID: <CAPTiy3NY7oB0g4fg_nmsF8YzzPRdMh2aFnezy5ceoKiM8UWW8w@mail.gmail.com>
Subject: Re: Native symlinks and setup.exe
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes

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 AT thorstenkampe DOT 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