Warren Young:

> By that reckoning, I’d rank *.lnk above Cygwin symlinks in many
> regards. Why wouldn’t that work?

Handling Windows Shell Links (*.lnk) can be tricky:

There's built-in logic to resolve links to missing targets (called
"link tracking", can be disabled). That's why portability of *.lnk
files may be limited across machines, and Fossil would have to keep
the link information separately, and create *.lnk files as needed.

https://technet.microsoft.com/en-gb/magazine/2009.10.windowsconfidential.aspx

Also, there's other *.lnk file options that may affect portability:

https://msdn.microsoft.com/en-us/library/windows/desktop/bb762540.aspx

--Florian
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to