Re: [PATCH 1/2] Treat Windows Store's "app execution aliases" as symbolic links

I am skeptical about this patch (part 1), interposing appexec reparse point data as symlinks for cygwin applications. The appexec reparse point data is essentially an extended attribute holding data that is used by CreateProcess(), more like a windows .lnk file or an X11 .desktop file, not

[PATCH 2/2] Allow executing Windows Store's "app execution aliases"

The Windows Store version of Python (and apparently other Windows Store applications) install a special reparse point called "app execution alias" into the user's `PATH`. These applications can be executed without any problem, but they cannot be read as if they were files. This trips up Cygwin's b

[PATCH 1/2] Treat Windows Store's "app execution aliases" as symbolic links

When the Windows Store version of Python is installed, so-called "app execution aliases" are put into the `PATH`. These are reparse points under the hood, with an undocumented format. We do know a bit about this format, though, as per the excellent analysis: https://www.tiraniddo.dev/2019/09/overv

[PATCH 0/2] Handle "app execution aliases"

When installing e.g. Python via the Windows Store, it is common that the `python3.exe` entry in the `PATH` is not actually an executable at all, but an "app executaion alias" (i.e. a special class of reparse point). These filesystem entries are presented as 0-size files, but they are not readable,