From: jacob <jacob@cda61777-01e9-0310-a592-d414129be87e>
Date: Mon, 9 Aug 2004 17:01:25 +0000 (+0000)
Subject: Apparently sending the tar output to stdout rather than a file causes tar to
X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/commitdiff_plain/a8a420c5fe4fab24df960cc086571812ac88b148?hp=4cf69d46bc9a7ff6b812edf2d5f282afd789a69a

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.


git-svn-id: svn://svn.tartarus.org/sgt/putty@4429 cda61777-01e9-0310-a592-d414129be87e
---

diff --git a/mkunxarc.sh b/mkunxarc.sh
index 78f4b360..a2907954 100755
--- a/mkunxarc.sh
+++ b/mkunxarc.sh
@@ -43,5 +43,5 @@ if test "x$ver" != "x"; then
    md5sum `find . -name '*.[ch]' -print` > manifest;
    echo "$ver" > version.def)
 fi
-tar -C uxarc -chzf - $arcname > $arcname.tar.gz
+tar -C uxarc -chzof $arcname.tar.gz $arcname
 rm -rf uxarc