Hi Andrey,
Am 01.03.2020 um 02:52 schrieb Andrey Repin:
>> I try to reliably determine if native Windows symlink are working for a
>> current cygwin environment in a shell script.
>
>> Therefor I used a powershell snipped:
>
>> mkdir asdfgh
>> ln -s asdfgh/ asdfgh-1
>> powershell "& {Get-Item -Path asdfgh-1 | Select-Object}"
>
>> On cygwin 3.0.7 the output is as follows:
>
>
>> Directory: D:\cygwin\home\rainer\temp
>
>
>> Mode LastWriteTime Length Name
>> ---- ------------- ------ ----
>> d----l 29.02.2020 13:58 asdfgh-1
>
>> On cygwin 3.1.4 I get:
>
>
>> Directory: D:\cygwin\home\rainer\temp
>
>
>> Mode LastWriteTime Length Name
>> ---- ------------- ------ ----
>> d---- 29.02.2020 13:58 asdfgh-1
>
>> So now there is no indication that this is a link. Is this new behaviour
>> intended or a bug?
>
>> I did not try on Windows 10, I'm still on windows 7.
>
> I get the same behavior is not using Cygwin to create the link at all, this is
> probably a change in how Cygwin interprets symlinks.
I don't know what's going on here. The only difference is the cygwin
version. So, the different behaviour is caused by cygwin while creating
the link, for sure!Somebody any idea? Rainer
signature.asc
Description: OpenPGP digital signature
