Thread (2 messages) 2 messages, 2 authors, 2021-06-07

Re: [PATCH] t0001: fix broken not-quite getcwd(3) test in bed67874e2

From: Ævar Arnfjörð Bjarmason <hidden>
Date: 2021-06-07 11:31:18

Possibly related (same subject, not in this thread)

On Wed, Jun 02 2021, Junio C Hamano wrote:
René Scharfe [off-list ref] writes:
quoted
quoted
On AIX under both bash and ksh this test breaks because "pwd -P" will
happily display the current working directory, but getcwd(3) called by
the "git init" we're testing here will fail to get it.

I checked whether clobbering the $PWD environment variable would
affect it, and it didn't. Presumably these shells keep track of their
working directory internally.

Let's change the test to a new "test-tool getcwd".
Makes sense.

If /bin/pwd can figure out the path to the current working directory
without read permissions to parent directories then it might be possible
to teach strbuf_getcwd() the same trick, though.  How does it do it?
...
If strbuf_getcwd() were to learn any of these tricks, then so would
"test-tool getcwd", via its xgetcwd() call.  At that point we'd better
rename GETCWD_IGNORES_PERMS to XGETCWD_IGNORES_PERMS.

But I guess we need none of that because we never got a request from
an AIX user to support a /home directory without read permissions,
right?
Nice "thinking aloud".
I see (well, rc/release period and all) that you didn't pick this up. I
think per my just-sent
http://lore.kernel.org/git/871r9d6hhy.fsf@evledraar.gmail.com (local) that it
makes sense to just leave this at s/pwd(1)/getcwd(3)/ as this patch
does.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help