-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 10/4/2009 2:19 PM:
> The Cygwin symlink(2) call does not add the .exe suffix, neither in
> Cygwin 1.5, nor in Cygwin 1.7. It looks like a feature of the ln(1)
> tool from the Cygwin 1.5 coreutils, AFAICS.
Yes, the 1.5
David Antliff wrote:
In my experience, it should be possible to create symlinks to any
arbitrary target, regardless of whether it actually exists or not.
Therefore, if I create a symlink to "/bin/ls" then I'd expect that to
be the content of the symlink - the automatic behaviour of rewriting
it t
On Oct 5 09:12, David Antliff wrote:
> 2009/10/5 Vincent Rivière :
> > Do you agree this is a bug and it should be fixed ?
>
> I've got nothing to do with the code, but I am an interested observer.
>
> In my experience, it should be possible to create symlinks to any
> arbitrary target, regardle
2009/10/5 Vincent Rivière :
> Do you agree this is a bug and it should be fixed ?
I've got nothing to do with the code, but I am an interested observer.
In my experience, it should be possible to create symlinks to any
arbitrary target, regardless of whether it actually exists or not.
Therefore,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Vincent Rivière on 10/4/2009 6:21 AM:
> $ ln -s /bin/ls lls
> $ ls -l lls
> lrwxrwxrwx 1 vincent cygwin 11 Oct 4 14:13 lls -> /bin/ls.exe
>
> Do you agree this is a bug and it should be fixed ?
I'm not sure whether I agree that it is a
Hello.
I have just noticed the following behavior in Cygwin 1.5.25-15:
$ ln -s /bin/ls lls
$ ls -l lls
lrwxrwxrwx 1 vincent cygwin 11 Oct 4 14:13 lls -> /bin/ls.exe
I think the link target should not show the .exe
For example, if I make on Cygwin a tar archive containing symlinks to
well-know
6 matches
Mail list logo
