> PR 44498 is regarding tar(1)'s dependence on getcwd(3). > This only exists when /bin/pax is called as "tar", [...]
> Testing: [...] > $ tar tfv - This is just one of many cases that exhibited the issue. It is one of the least excusable, because it has no need to touch the filesystem at all, but there are plenty of others, such as "tar cf - ." (which, while it does use the filesystem, also has no justification for caring what its working directory is). Of course, if current tar(1) doesn't suffer from this, the symptom as described is gone - but if pax-when-run-as-tar still exhibits it, then it is still a bug, just a bug in pax rather than a bug in tar. > It probably makes more sense to just close this PR. I think it would make more sense to reclassify it as a PR against pax rather than a PR against tar. (Especially if pax exhibits a similar insistence on getcwd() working even when run as pax. I don't know whether it does; I don't run anything recent enough to usefully test it on, and I don't even know pax-as-pax enough to test it anyway.) /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML mo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
