Re: Cygwin doesn't support IO_REPARSE_TAG_APPEXECLINK

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

On Jun  9 21:18, Martin Rauscher via Cygwin wrote:
> > Not clear why you expect that a Windows specific tag as
> > IO_REPARSE_TAG_APPEXECLINK should be supported on a Posix platform ?
> >
> > Moreover all the documentation from MS seems
> >
> > https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/c8e77b37-3909-4fe6-a4ea-2b9d423b1ee4
> >
> > that seems a bit short to help third party in properly using it.
> >
> > Regards
> > Marco
> 
> 
> For some context, the reason why this is getting some attention is
> (probably) this:
> Windows is getting its own Package Manager and it's based on UWP and
> thus this issue appears for everybody trying out WinGet + Cygwin (or
> Git for Windows etc).
> Issue on their side: https://github.com/microsoft/winget-cli/issues/228
> 
> This is truly a pretty weird feature of Windows/NTFS where there was
> not much reason to support it before, but with WinGet this will become
> a much requested feature on no time.

Two questions:

- Do you expect Cygwin to handle IO_REPARSE_TAG_APPEXECLINK reparse
  points as ordinary executable files, or as symlinks pointing to
  executable files?

- If as symlinks, we'd need somebody to run the test app from
  https://cygwin.com/pipermail/cygwin/2020-March/244180.html on such
  symlinks, to see how they look on the inside.  This is required to let
  Cygwin handle them as symlinks correctly.


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer