]> asedeno.scripts.mit.edu Git - PuTTY.git/commit
Apparently sending the tar output to stdout rather than a file causes tar to
authorJacob Nevins <jacobn@chiark.greenend.org.uk>
Mon, 9 Aug 2004 17:01:25 +0000 (17:01 +0000)
committerJacob Nevins <jacobn@chiark.greenend.org.uk>
Mon, 9 Aug 2004 17:01:25 +0000 (17:01 +0000)
commitaaeca0f4a005be92798e700a82857d9addef3ac5
tree8d53b260d0d0d7dbfc08c6e930c44981ce297c3e
parentc7648cd296c82cfecfda2a7370719750fc824478
Apparently sending the tar output to stdout rather than a file causes tar to
pad with trailing NULs, which slightly upsets old versions of gzip (1.2.4,
not 1.3.x), which upsets some of our correspondents.
Use -f to send it to a file instead. (It's not transparently clear what
happens when you mix -f and -C; I've tested this with ixion's tar, 1.13.25.)

Also add option -o to generate POSIX tar files, as for halibut/Makefile;
apparently this shuts up a `trailing garbage' error from WinZip.

[originally from svn r4429]
mkunxarc.sh