Hello Phil,
I have a question to -i SYMLINKS on Windows (in my case Windows 10).
In help I found infos that it should only work for directories.
For file-symlinks something like: -if '$FileAttributes !~ ... should be used.
For test purposes I have created such a directory-symlink with mklink /d ...
But I have seen that -i SYMLINKS (in combination with -r) does not work.
Exiftool follows the links and changes files in "destination folder" of the symlink.
As I have found no detailed information about -i SYMLINKS for Windows I ask this question:
Is it an error or is it not supported on Windows.
If it is not supported
- this should be noticed in help.
- is there another possibility to reach the goal.
Thanks for your help in advance
Best regards
herb
Hi Herb,
Thanks for this report.
I'll test this in Windows when I get a chance.
- Phil
I've tested this. It works as expected running in cygwin under Windows 10, but fails to detect the symbolic link running in a cmd shell.
Apparently there is an ugly work-around: https://stackoverflow.com/questions/50244042/perl-detecting-symbolic-links-under-windows-10 (https://stackoverflow.com/questions/50244042/perl-detecting-symbolic-links-under-windows-10)
But this work-around would treat directory hard links incorrectly.
I would prefer not to implement an ugly patch like this unless there is a real need. My feeling is that symlinks in Windows are not very common... Multiply this by the percent of people who would want to use -i SYMLINKS and you get a very small number.
- Phil
Hello Phil,
thanks for your investigations.
QuoteI would prefer not to implement an ugly patch like this unless there is a real need.
I understand and agree.
Best regards
herb