https://bugs.winehq.org/show_bug.cgi?id=50586
--- Comment #22 from Zebediah Figura z.figura12@gmail.com --- (In reply to Erich E. Hoover from comment #21)
(In reply to Zebediah Figura from comment #20)
(In reply to Erich E. Hoover from comment #19)
...
(Note also that we've already reported directory symlinks as FILE_ATTRIBUTE_REPARSE_POINT since forever, though we haven't implemented really any of the other behaviour surrounding that.)
Right, so I would say my first priority should be to fix this bug by making the unix symlinks fully transparent again (ignore FILE_OPEN_REPARSE_POINT) since that's been our baseline for some time. If we run into some applications that actually care then it would not be too much trouble to change and report them "properly", so we could always re-evaluate at that point.
Eh, so I'm kind of trying to ask if this is the right solution. I.e. can we fix this by translating unix symlinks to regular NT symlinks always, and implementing FILE_OPEN_REPARSE_POINT appropriately, and will that have negative consequences?