DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=Ye/QbJcEszWGBJRT6peIA449ATGg
	V7YvQjNrjh+znPNVllhM1j1yc3M+uFNDcHZO7QPryBQTpLd/6MYi5hn0rC4o44KX
	NQZ5IIMtRK6yrYr2zmJZV48rcGmbO0PcFEw5QNQLzbDZdwdjSnP5Hbx3eMWbJVSi
	lGiKH6NokXq+k+k=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Native symlinks and setup.exe
From: Vince Rice <vrice@solidrocksystems.com>
In-Reply-To: <CAPTiy3M+C9H41K65e0Dyqqc+AUismTrPGwmoCmNQc=-Gv++NYQ@mail.gmail.com>
Date: Tue, 4 Oct 2016 15:53:44 -0500
Message-Id: <DD849478-5A57-441D-B6C8-6A1488E80FA0@solidrocksystems.com>
References: <CAPTiy3O9eEhdgWcdEKkY=Egd+_8WJtxOc6WXjhecr9Du=-f=fg@mail.gmail.com> <nsqpd6$tvm$2@blaine.gmane.org> <CAPTiy3NY7oB0g4fg_nmsF8YzzPRdMh2aFnezy5ceoKiM8UWW8w@mail.gmail.com> <nsthp6$jtq$1@blaine.gmane.org> <CAPTiy3NzXWSv8+kazpeXYx9EB18nQ+f+S1aSyQcAF4aMrNdqtQ@mail.gmail.com> <CA+Fg1xbhdZkexKwEFYmy-BtQdV5ZPYOeJC9K-F0Kdh0V701zBg@mail.gmail.com> <CAPTiy3M+C9H41K65e0Dyqqc+AUismTrPGwmoCmNQc=-Gv++NYQ@mail.gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Content-Transfer-Encoding: 8bit

Please don’t https://cygwin.com/acronyms/#TOFU.

> On 4 October 2016 at 17:56, Gerrit Haase <gerrit.haase@gmail.com> wrote:
>> Hello Gene,
>> 
>> in my opinion, it is not a setup.exe or tar problem, but I think
>> packages should not include symlinks at all. All can be created
>> postinstallation by the postinstall script, inside Cygwin and the
>> users environment it is running on.
>> 
>> Obviously, a political discussion is required, to decide whether it is
>> ok, as is, or if a change in package logic would have benefits.
> 
> On Oct 4, 2016, at 3:41 PM, Gene Pavlovsky <gene.pavlovsky@gmail.com> wrote:
> 
> That is a good point as well, however I'm not sure what are the
> opinions of Cygwin's "elders".
> Would everyone vote for creating a policy like that and pushing it to
> the package maintainers?
> A political discussion is what I'm trying to start here :)

I am not a “Cygwin elder,” nor do I play one on TV.

Packages are going to include simlinks because packages have simlinks in them.
The goal of Cygwin is to minimize the work that has to be done to port a package.
For example, the gawk package includes a link to awk. And so forth.

I don’t see that changing. And, as already noted, setup isn’t a Cygwin program,
so it knows (and cares) nothing about cygwin environment variables.


--
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