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=W4dGiaP
	poUpPAgNXOoTTZGrWZiBIJgH5+YRz9CCRoCFUvoxNR+5i0xdMpVaLtGN01jtpYSt
	e4okvyNHcYO5rnPVzF0pafur5hMVAS97EGUdcBWq9DtOURdqH0iqKCRNUmP0tsqL
	bbI1CFVTPom9BgPLdor9Fk9TJbjo2eYAuq6c=
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=jOjhzPZGYFpIm
	yVi/aQrS7qFRzA=; b=eWa/ONKyffTkadprpP6fQXL3EZl+gsgwRGa3dlpkjrAb1
	Savj6D0Cs8uMDekeRN2RMem5l79yqTbF0XTXmi6bKIR7yol7xfgjfBW8V6EuqDid
	KuqLMvJAs9AFjeTx8QOhL+OtRKyjtopupKgFxjNUjvgZS272smRwO7I625/MrQ=
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=-1.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=exclusively, H*f:sk:nsthp6$, H*i:sk:nsthp6$, Far
X-HELO: mail-io0-f172.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=Jz+AniqfN6YDtJ0/X2dO8mBFEe/X+Z7/Pv23b82OlEQ=;        b=OffgTi9vjr5MOdwsW4vaSSwGt2AgygLHuLRYvG4k9LUoyZu0Ckq3cMYjCqFSj+iHl7         Ymvx7DR/BQrx5HK8wT9A4bE1tanA/TDiYCNzCdBHqZYbDS6SmRyuGCDf7bi+JEbWorr1         8+lWmsdvd/GrKeZpbnkqMQb4t0rX6Xc35QZt4otu4GMbMYDMeX7ElMCLjChesJ4ElViB         k2ibZQ77PMul95zYRo80exO+rgo4Ll372lwR5O5Q27qEmCy8NpYNDI4Cv1fgrQ2+NUEc         ybO3Qo0Oryp5/7bykjFTkztiqGaxHUDx2sptoRjoAEMHOx5rpxlW5gIWvVcdSjP65i4N         jlXw==
X-Gm-Message-State: AA6/9RkhBeomk1AQiUAm27Q4559buyLdJ2WaBoU5hraNcYNwqWENqFjLNzj+bKnq2UFv5sq2+L//gxEaHtryyA==
X-Received: by 10.107.142.147 with SMTP id q141mr713404iod.67.1475529358358; Mon, 03 Oct 2016 14:15:58 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <nsthp6$jtq$1@blaine.gmane.org>
References: <CAPTiy3O9eEhdgWcdEKkY=Egd+_8WJtxOc6WXjhecr9Du=-f=fg AT mail DOT gmail DOT com> <nsqpd6$tvm$2 AT blaine DOT gmane DOT org> <CAPTiy3NY7oB0g4fg_nmsF8YzzPRdMh2aFnezy5ceoKiM8UWW8w AT mail DOT gmail DOT com> <nsthp6$jtq$1 AT blaine DOT gmane DOT org>
From: Gene Pavlovsky <gene DOT pavlovsky AT gmail DOT com>
Date: Tue, 4 Oct 2016 00:15:57 +0300
Message-ID: <CAPTiy3NzXWSv8+kazpeXYx9EB18nQ+f+S1aSyQcAF4aMrNdqtQ@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

That makes sense but it would be a LOT of work for many people (well,
a lot of small work for many people).

How about this kind of modification for the setup program: extract tar
archives into temp dir, after that search that temp dir for symlinks,
if they don't match the current winsymlinks option, recreate them
appropriately?

I just remembered what I did when I first discovered the winsymlinks
option (already having a 32-bit Cygwin set up for a couple of years).
I tarred my entire cygwin directory, copied it over to my Linux
server, untarred it there - which created all the symlinks, including
Cygwin's symlinks, as proper symlinks, then tarred it back, copied
back to the Windows box, untarred - voila, all symlinks are created as
native. I wonder how are Cygwin vs native symlinks stored inside tar
archive - tar knows they are symlinks but also knows which ones are
native vs Cygwin's. That's a whole lot of bother, though, and now that
I know that some further package update down the line might replace
native links with Cygwin links again (didn't expect that), I wouldn't
be willing to go to that trouble.

It should work out of the box automatically, in my opinion. Cygwin
symlinks are a kluge (e.g. I can't edit them in Far manager, the way I
can adjust a native symlink), and if using Cygwin exclusively on NTFS
filesystems, supporting symlinks, I can't see any reason to have any
on my system. The proposed solution is sensible, but it spreads
responsibility among all the package maintainers, and it will take a
long time to reach.

On 3 October 2016 at 15:08, Thorsten Kampe <thorsten AT thorstenkampe DOT de> wrote:
> * Gene Pavlovsky (Mon, 3 Oct 2016 00:46:54 +0300)
>>
>> 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?
>
> Tar's task is to unpack what's in the archive. So converting is out
> of question. You can ask the maintainer of the affected packages to
> create the symlinks in the postinstall script.
>
> 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