From e3b237261ba2de69cc93727c4a2b9de6d11348d0 Mon Sep 17 00:00:00 2001 From: Tim Kientzle Date: Sat, 30 May 2009 03:38:01 -0400 Subject: [PATCH] Comment tweaks; make it a little more obvious the difference between examples/untar.c and contrib/untar.c. I should probably rename one of these. SVN-Revision: 1144 --- examples/untar.c | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/examples/untar.c b/examples/untar.c index 88f6dc26d..468c1079e 100644 --- a/examples/untar.c +++ b/examples/untar.c @@ -4,15 +4,16 @@ */ /* - * This is a compact tar extraction program whose primary goal is - * small size. Statically linked, it can be under 64k, depending on - * how cleanly factored your system libraries are. Note that this - * uses the standard libarchive, without any special recompilation. - * The only functional concession is that this program uses the - * uid/gid from the archive instead of doing uname/gname lookups. - * (Call archive_write_disk_set_standard_lookup() to enable - * uname/gname lookups, but be aware that this can add 500k or more to - * a static executable, depending on the system libraries.) + * This is a compact tar extraction program using libarchive whose + * primary goal is small executable size. Statically linked, it can + * be under 64k, depending on how cleanly factored your system + * libraries are. Note that this uses the standard libarchive, + * without any special recompilation. The only functional concession + * is that this program uses the uid/gid from the archive instead of + * doing uname/gname lookups. (Call + * archive_write_disk_set_standard_lookup() to enable uname/gname + * lookups, but be aware that this can add 500k or more to a static + * executable, depending on the system libraries.) * * To build: * gcc -static -Wall -o untar untar.c -larchive -- 2.47.3