From: Jeremy Drake <cygwin@jdrake.com>
To: cygwin@cygwin.com
Cc: Orgad Shaneh <orgads@gmail.com>
Subject: realpath issue with native[strict] symlinks
Date: Fri, 14 May 2021 21:12:46 -0700 (Pacific Daylight Time) [thread overview]
Message-ID: <alpine.WNT.2.22.394.2105142102180.10796@persephone> (raw)
I apologize for not replying to the message properly, I am not subscribed
and am copy-pasting from web archive.
On Sat, May 8, 2021 at 12:20 AM Corinna Vinschen wrote:
> The changes have a behavioral change, but I think this is for the
> better: Virtual drives are not treated as drives anymore, but as
> symlinks. Given they are just pointers to other drives or directories,
> tha't much closer to reality. I. e., in case of my above virtual drive
> T:, what you'll see in the /cygdrive dir (unless your cygdrive prefix is
> / only) is this:
I am concerned about this behavior. The reason I was using subst to begin
with was that some build tools encode the full path in their filenames,
resulting in hitting MAX_PATH-related issues for not horribly long/deep
paths. With this change, running a native Windows process (MinGW-w64)
from a subst drive results in what it sees as the CWD being 'dereferenced'
as though subst was not used, defeating the path-shortening purpose.
For instance, using your example mapping:
> $ ls -lG /cygdrive
> total 16
> d---r-x---+ 1 TrustedInstaller 0 Apr 29 21:07 c
> drwxr-xr-x 1 corinna 0 Dec 31 1979 e
> lrwxrwxrwx 1 corinna 32 May 6 20:43 t -> /cygdrive/c/cygwin64/home/corinna/tmp
Prior to these changes would show
$ cd /cygdrive/t && cmd /c cd
T:\
But after these changes would show
$ cd /cygdrive/t && cmd /c cd
C:\cygwin64\home\corinna\tmp
This path could well be long enough to trigger build issues for certain
MINGW-packages.
Sorry to be a nuisance...
next reply other threads:[~2021-05-15 4:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 4:12 Jeremy Drake [this message]
2021-05-17 10:12 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2021-05-27 20:21 Jeremy Drake
2021-05-28 19:23 ` Jeremy Drake
2021-06-08 0:01 ` Jeremy Drake
2021-05-18 20:01 Jeremy Drake
2021-05-19 12:42 ` Corinna Vinschen
2021-04-27 5:44 Orgad Shaneh
2021-05-04 19:52 ` Orgad Shaneh
2021-05-06 17:44 ` Corinna Vinschen
2021-05-06 18:36 ` Orgad Shaneh
2021-05-07 21:20 ` Corinna Vinschen
2021-05-09 11:35 ` Orgad Shaneh
2021-05-10 7:50 ` Corinna Vinschen
2021-05-12 7:10 ` Andrey Repin
2021-05-12 8:14 ` Corinna Vinschen
2021-04-18 7:59 Orgad Shaneh
2021-04-19 12:58 ` Corinna Vinschen
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=alpine.WNT.2.22.394.2105142102180.10796@persephone \
--to=cygwin@jdrake.com \
--cc=cygwin@cygwin.com \
--cc=orgads@gmail.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).