https://bugs.winehq.org/show_bug.cgi?id=50586
--- Comment #11 from Zebediah Figura z.figura12@gmail.com --- (In reply to Erich E. Hoover from comment #10)
(In reply to Zebediah Figura from comment #9)
Note that a symlink can span file systems. It seems possible that a Windows application would be confused about a file residing on a different file system than its containing directory. That's already the case, and maybe not worth worrying about, but if we're going to make a grand final design of how symlinks work it might be worth taking into account...
Are you talking about applications that look for files based on inode? We could conceivably report the inode of the symlink in the case of a transparent symlink like this (and this is a feature that wouldn't be too hard to add in the future).
I'm not immediately sure it's the only problem, but it does come to mind as a concern. Note that the above solution won't work for directory symlinks.