> I get the feeling it's going to break all shar archives with binary files
shar encodes binary files. Here's what it does with a file that has contents: "foo\0bar\n":
sed 's/^X//' << 'SHAR_EOF' | uudecode &&
begin 600 foo.txt
(9F]O`&)A<@K.
`
end
SHAR_EOF
Interestingly, passing that heredoc to uudecode in the shell, it produces no output. However, if I pass the whole shar output to unshar, it does produce the file with the correct content.
shar encodes binary files. Here's what it does with a file that has contents: "foo\0bar\n":
Interestingly, passing that heredoc to uudecode in the shell, it produces no output. However, if I pass the whole shar output to unshar, it does produce the file with the correct content.