From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH v2 0/2] Handle "app execution aliases"
Date: Tue, 23 Mar 2021 22:04:25 +0100 (CET) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2103232152560.50@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <YFoQPRMwf1RYBufS@calimero.vinschen.de>
Hi Corinna,
On Tue, 23 Mar 2021, Corinna Vinschen wrote:
> On Mar 22 16:51, Johannes Schindelin via Cygwin-patches wrote:
> > 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, which is why Cygwin has problems to execute them, with the error
> > message "Permission denied".
> >
> > This issue has been reported a couple of times in the Git for Windows and
> > in the MSYS2 project, and even in Cygwin
> > (https://cygwin.com/pipermail/cygwin/2020-May/244969.html, the thread
> > devolved into a discussion about Thunderbird vs Outlook before long,
> > though).
> >
> > The second patch fixes that, and for good measure, the first patch teaches
> > Cygwin to treat these reparse points as symbolic links.
> >
> > Changes since v1:
> >
> > - Introduce and use `struct _REPARSE_APPEXECLINK_BUFFER`.
> >
> > Johannes Schindelin (2):
> > Treat Windows Store's "app execution aliases" as symbolic links
> > Allow executing Windows Store's "app execution aliases"
> >
> > winsup/cygwin/path.cc | 40 ++++++++++++++++++++++++++++++++++++++++
> > winsup/cygwin/spawn.cc | 7 +++++++
> > 2 files changed, 47 insertions(+)
>
> I decided to apply this now, while we're still discussing the osf handle
> problem.
>
> Pushed with two fixes. I prepended "Cygwin:" to the git log subject and
> I patched this compile time problem:
>
> path.cc: In function ‘int check_reparse_point_target(HANDLE, bool, PREPARSE_DATA_BUFFER, PUNICODE_STRING)’:
> path.cc:2581:25: error: ‘struct _REPARSE_APPEXECLINK_BUFFER’ has no member named ‘Strings’
> 2581 | WCHAR *buf = rpl->Strings;
> | ^~~~~~~
Uh oh. Sorry for the breakage. I thought I had test-compiled it...
Apparently I didn't (or I ignored a warning or something).
>
> I also added this to the release notes.
Thank you!
Ciao,
Johannes
prev parent reply other threads:[~2021-03-23 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 15:11 [PATCH " Johannes Schindelin
2021-03-22 15:51 ` [PATCH v2 " Johannes Schindelin
2021-03-22 15:51 ` [PATCH v2 1/2] Treat Windows Store's "app execution aliases" as symbolic links Johannes Schindelin
2021-03-22 15:51 ` [PATCH v2 2/2] Allow executing Windows Store's "app execution aliases" Johannes Schindelin
2021-03-23 15:58 ` [PATCH v2 0/2] Handle " Corinna Vinschen
2021-03-23 21:04 ` Johannes Schindelin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.2103232152560.50@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=cygwin-patches@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).