-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Krzysztof Duleba on 12/12/2005 3:35 AM: > > And ln -s -f a b produces b ==> a if a.exe doesn't exist yet.
You are correct that the behavior of cygwin ln in the presence of symlinks has not been consistent in the past. I think the current behavior (in 5.3.0-9 or 5.93-1) is the most sane - if linking to an existing file, .exe is appended to the link if the existing file had .exe; otherwise, nothing is done. There is also the cygwin-specific --disable-exe-magic option to bypass .exe magic when creating symlinks. Beyond that, once a symlink was created (either by the packager, or by a postinstall script) with inconsistent use of .exe using an older version of ln, or by creating the symlink before the .exe, you will run into these potential issues. Let me know if I need to do any further looking into the behavior of ln, or whether this particular symlink issue is taken care of by reinstallation and/or improved exim postinstall scripts. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] volunteer cygwin coreutils maintainer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDnXkp84KuGfSFAYARAh9fAJ4hL738QgCab8YuVrmo1oKq9MAKcQCcDAah C386z5tdnTH2wtWxACq4nCE= =IDSY -----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/
