> -----Original Message-----
> From: Larry Hall (RFK Partners, Inc) [mailto:[EMAIL PROTECTED]]
> 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/
