aboutsummaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorRon Yorston <rmy@pobox.com>2022-09-27 08:43:26 +0100
committerRon Yorston <rmy@pobox.com>2022-09-27 11:18:29 +0100
commita55cf07365ec2ff51749a77e09ae9edac79a99fe (patch)
tree145ab6d27987d063cbdc72b93152a141c1bd0b49 /arch
parent1b3002fb63f83498d210cfb1cc189313df0eb8c5 (diff)
downloadbusybox-w32-a55cf07365ec2ff51749a77e09ae9edac79a99fe.tar.gz
busybox-w32-a55cf07365ec2ff51749a77e09ae9edac79a99fe.tar.bz2
busybox-w32-a55cf07365ec2ff51749a77e09ae9edac79a99fe.zip
libarchive: alter handling of failure to create symlinks
Unlike GNU tar upstream BusyBox tar treats all errors as fatal. Failure to create a symlink on Windows is very likely due to a lack of the required privilege. busybox-w32 therefore treats this case as a non-fatal error and, as far as possible, continues extracting files. However: - The inconsistency of this behaviour caused some confusion. - busybox-w32 tar didn't return an error status when a non-fatal error was encountered, unlike GNU tar. Change the implementation so extraction continues when symlink creation fails but the error report is deferred until all of the archive has been processed. Only one error is reported and it's treated as fatal. Saves 48-64 bytes. (GitHub issue #265)
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions