-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Eric Backus on 8/24/2007 2:24 PM: > Eric Blake <ebb9 <at> byu.net> writes: > >> No, it is not an old-style link, because it has the .lnk suffix when >> viewed via Windows. However, it is not a link that would normally be >> created by the current coreutils, since I have added some .exe magic into >> ln when symlinking against existing .exes: > >>From this I guess that the .exe magic is currently in the code for each > program that might create a symlink. Is there any way that the .exe magic > could be moved to inside the symlink() function call, so that it > automatically > works for all programs that create symlinks? Or does that introduce other > problems?
Most .exe magic is already inside cygwin. In particular, CVS cygwin (which will become 1.7.0) has a transparent_exe option that makes this all even cleaner, without application specific knowledge. Coreutils is special, in that it tends to do a lot of low-level tasks where the .exe magic provided by cygwin is not always smart enough (for example, cp /bin/bash /bin/sh needs to add .exe), at the expense of making usage patterns of more common upper-level applications do the right thing by default. But the real problem reported by this thread has nothing to do with .exe magic after all. Rather, it had to do with a non-compliant implementation of open(O_CREAT|O_EXCL). In other words, to date, I have not had to teach tar about any special .exe magic. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGz0Qw84KuGfSFAYARAsWnAKDY0PFvT83HjLYsNVd89GE9Bkm3zwCgmUIn fOJklfUULT+2gqYlY1nkRCI= =/SPe -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
