version 1.3 10, problem with gunzip.exe

Larry Hall (RFK Partners, Inc) lhall@rfk.com
Tue May 21 11:48:00 GMT 2002


At 06:49 PM 5/20/2002, Robert Collins wrote:


> > -----Original Message-----
> > From: Robert Collins 
> > Sent: Tuesday, May 21, 2002 8:46 AM
> > 
> > >    2. I believe setup.exe creates symbolic links as if
> > > "nowinsymlinks" is 
> > >       set.  So setup would create the symbolic links as 
> > > Cygwin symlinks 
> > >       rather than Windows shortcuts regardless of the 
> > setting in the 
> > >       CYGWIN environment variable.
> > 
> > 2 is wrong.
>
>Actually, 2 is right. Setup could do either though.



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?! ;-)





Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


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



More information about the Cygwin mailing list