mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

improve comment

Browse source
This commit is contained in:
Joey Hess 2021-01-13 12:55:26 -04:00
parent 0ec7bed3c6
commit a7c56f84fc
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 2 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/bugs/git-annex_get__58___createDirectory__58___does_not_exist/comment_2_020d7c6292c2a8238a5ec891fba9eddd._comment
View file

@ -5,24 +5,13 @@
content="""
Is the relative path actually valid? There may be some case involving
symlinks in the parent directories where the relative path could be wrong.
This part seems to suggest there are symlinks involved:
I am not familiar with /private on OSX. Is the problem something like,
the user can access /private/foo/bar but not /private/foo, and so a
relative path traversing that can't find the ".." in that directory?
If so, then a relative path from /private/foo/bar to /private/foo/baz would
also fail and that case would not be helped by using an absolute
path to a different top level directory.
> some of these folders actually live in /private/var, despite being accessible via /var
Of course, it's a bit surprising that a relative path is used when the path
is into an entirely different top-level directory. But without
understanding the problem I don't know if switching to using an absolute
path in that case would only happen to fix this case of the problem and not
the general case, whatever that is.
It's worth noting that git fails if a parent directory does not have
the x bit set:
joey@darkstar:/tmp/foo/bar/baz>git init
fatal: Invalid path '/tmp/foo/bar': Permission denied
"""]]