Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: version 1.3 10, problem with gunzip.exe
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
Date: Wed, 22 May 2002 19:47:37 +1000
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C6135@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>, <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4M9tSA11235



> -----Original Message-----
> From: Larry Hall (RFK Partners, Inc) [mailto:lhall AT rfk DOT com] 
> Sent: Wednesday, May 22, 2002 1:00 AM

> I guess I can see some value to having the symlinks that 
> setup generates be windows shortcuts.  The obvious plus is 
> that symbolic links to executables and other files should be 
> understood in non-Cygwin shells.  Still, while this is an 
> advantage for those packages that make using of symbolic links for 
> things like this, it's unclear to me that making such a 
> change would result in 
> something intuitive, since the user would need to add ".lnk" to the 
> executable name ("gunzip.exe.lnk" in this case) to get it to 
> work in an non- Cygwin shell.  But probably it's a plus 
> overall since using the Windows shortcuts at least allows for 
> the use of the symlink in non-Cygwin shells, despite the 
> clunkiness of its usage.  In the current case, this is not true.
> 
> There's a nice bit of philosophy for you, don't you think?! ;-)

Yes :}. We initially left setup unchanged because the long term
existence of windows shortcuts wasn't clear, and we had to be backward
compatible. I think we are far enough beyond that that we could accept
patches to alter the behaviour.

Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/