Adding upstream version 0.10.

Signed-off-by: Daniel Baumann <daniel@debian.org>

doc/tarlz.info

@@ -11,7 +11,7 @@ File: tarlz.info,  Node: Top,  Next: Introduction,  Up: (dir)
 Tarlz Manual
 ************
 
-This manual is for Tarlz (version 0.9, 22 January 2019).
+This manual is for Tarlz (version 0.10, 31 January 2019).
 
 * Menu:
 
@@ -120,6 +120,13 @@ archive 'foo'.
      the archive if no FILES have been specified. Tarlz can't
      concatenate uncompressed tar archives.
 
+'-B BYTES'
+'--data-size=BYTES'
+     Set target size of input data blocks for the '--bsolid' option.
+     Valid values range from 8 KiB to 1 GiB. Default value is two times
+     the dictionary size, except for option '-0' where it defaults to
+     1 MiB.
+
 '-c'
 '--create'
      Create a new archive from FILES.
@@ -190,6 +197,18 @@ archive 'foo'.
      members it creates, reducing the amount of memory required for
      decompression.
 
+     Level   Dictionary size   Match length limit
+     -0      64 KiB            16 bytes
+     -1      1 MiB             5 bytes
+     -2      1.5 MiB           6 bytes
+     -3      2 MiB             8 bytes
+     -4      3 MiB             12 bytes
+     -5      4 MiB             20 bytes
+     -6      8 MiB             36 bytes
+     -7      16 MiB            68 bytes
+     -8      24 MiB            132 bytes
+     -9      32 MiB            273 bytes
+
 '--asolid'
      When creating or appending to a compressed archive, use appendable
      solid compression. All the files being added to the archive are
@@ -197,6 +216,15 @@ archive 'foo'.
      are compressed into a separate lzip member. This creates a solidly
      compressed appendable archive.
 
+'--bsolid'
+     When creating or appending to a compressed archive, compress tar
+     members together in a lzip member until they approximate a target
+     uncompressed size.  The size can't be exact because each solidly
+     compressed data block must contain an integer number of tar
+     members. This option improves compression efficiency for archives
+     with lots of small files. *Note --data-size::, to set the target
+     block size.
+
 '--dsolid'
      When creating or appending to a compressed archive, use solid
      compression for each directory especified in the command line. The
@@ -560,13 +588,13 @@ old tar programs from extracting the extended records as a file in the
 wrong place.  Tarlz also sets to zero those fields of the ustar header
 overridden by extended records.
 
-   If the extended header is needed because of a file size larger than
-8 GiB, the size field will be unable to contain the full size of the
-file. Therefore the file may be partially extracted, and the tool will
-issue a spurious warning about a corrupt header at the point where it
-thinks the file ends. Setting to zero the overridden size in the ustar
-header at least prevents the partial extraction and makes obvious that
-the file has been truncated.
+   If an extended header is required for any reason (for example a file
+size larger than 8 GiB or a link name longer than 100 bytes), tarlz
+moves the filename also to the extended header to prevent an ustar tool
+from trying to extract the file or link. This also makes easier during
+parallel extraction or listing the detection of a tar member split
+between two lzip members at the boundary between the extended header
+and the ustar header.
 
 
 4.3 As simple as possible (but not simpler)
@@ -626,10 +654,10 @@ to single-threaded mode and continues decoding the archive. Currently
 only the '--list' option is able to do multi-threaded decoding.
 
    If the files in the archive are large, multi-threaded '--list' on a
-regular tar.lz archive can be hundreds of times faster than sequential
-'--list' because, in addition to using several processors, it only
-needs to decompress part of each lzip member. See the following example
-listing the Silesia corpus on a dual core machine:
+regular (seekable) tar.lz archive can be hundreds of times faster than
+sequential '--list' because, in addition to using several processors,
+it only needs to decompress part of each lzip member. See the following
+example listing the Silesia corpus on a dual core machine:
 
      tarlz -9 -cf silesia.tar.lz silesia
      time lzip -cd silesia.tar.lz | tar -tf -            (5.032s)
@@ -690,9 +718,9 @@ Example 7: Extract files 'a' and 'c' from archive 'archive.tar.lz'.
 
 
 Example 8: Copy the contents of directory 'sourcedir' to the directory
-'targetdir'.
+'destdir'.
 
-     tarlz -C sourcedir -c . | tarlz -C targetdir -x
+     tarlz -C sourcedir -c . | tarlz -C destdir -x
 
 
 File: tarlz.info,  Node: Problems,  Next: Concept index,  Prev: Examples,  Up: Top
@@ -734,17 +762,18 @@ Concept index
 
 Tag Table:
 Node: Top223
-Node: Introduction1012
-Node: Invoking tarlz3124
-Node: File format10384
-Ref: key_crc3215169
-Node: Amendments to pax format20586
-Ref: crc3221110
-Ref: flawed-compat22135
-Node: Multi-threaded tar24508
-Node: Examples27012
-Node: Problems28682
-Node: Concept index29208
+Node: Introduction1013
+Node: Invoking tarlz3125
+Ref: --data-size4717
+Node: File format11536
+Ref: key_crc3216321
+Node: Amendments to pax format21738
+Ref: crc3222262
+Ref: flawed-compat23287
+Node: Multi-threaded tar25649
+Node: Examples28164
+Node: Problems29830
+Node: Concept index30356
 
 End Tag Table