From: Tim Kientzle Date: Sun, 10 Jan 2016 19:21:07 +0000 (-0800) Subject: Mention V7, a few wording tweaks X-Git-Tag: v3.1.900a~26 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=41358b275775cd7ff1b1b0076c7f1acf919f4ab3;p=thirdparty%2Flibarchive.git Mention V7, a few wording tweaks --- diff --git a/README b/README index 54a91e7eb..180d28459 100644 --- a/README +++ b/README @@ -13,7 +13,7 @@ Questions? Issues? This distribution bundle includes the following components: * libarchive: a library for reading and writing streaming archives * tar: the 'bsdtar' program is a full-featured 'tar' - replacement built on libarchive + implementation built on libarchive * cpio: the 'bsdcpio' program is a different interface to essentially the same functionality * cat: the 'bsdcat' program is a simple replacement tool for @@ -96,6 +96,7 @@ The library can create archives in any of the following formats: * "restricted" pax format, which will create ustar archives except for entries that require pax extensions (for long filenames, ACLs, etc). * Old GNU tar format + * Old V7 tar format * POSIX octet-oriented cpio * SVR4 "newc" cpio * shar archives @@ -130,12 +131,12 @@ Notes about the library architecture: * I've attempted to minimize static link pollution. If you don't explicitly invoke a particular feature (such as support for a - particular compression or format), it won't get pulled in. - In particular, if you don't explicitly enable a particular - compression or decompression support, you won't need to link - against the corresponding compression or decompression libraries. - This also reduces the size of statically-linked binaries in - environments where that matters. + particular compression or format), it won't get pulled in to + statically-linked programs. In particular, if you don't explicitly + enable a particular compression or decompression support, you won't + need to link against the corresponding compression or decompression + libraries. This also reduces the size of statically-linked + binaries in environments where that matters. * On read, the library accepts whatever blocks you hand it. Your read callback is free to pass the library a byte at a time