laag-xz 5.2.4.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.gitignore +57 -0
- data/LICENSE.txt +65 -0
- data/README.org +34 -0
- data/ext/laag/xz/extconf.rb +21 -0
- data/laag-xz.gemspec +20 -0
- data/lib/laag/xz.rb +29 -0
- data/vendor/git.tukaani.org/xz/.gitignore +66 -0
- data/vendor/git.tukaani.org/xz/AUTHORS +27 -0
- data/vendor/git.tukaani.org/xz/COPYING +65 -0
- data/vendor/git.tukaani.org/xz/COPYING.GPLv2 +339 -0
- data/vendor/git.tukaani.org/xz/COPYING.GPLv3 +674 -0
- data/vendor/git.tukaani.org/xz/COPYING.LGPLv2.1 +502 -0
- data/vendor/git.tukaani.org/xz/ChangeLog +7 -0
- data/vendor/git.tukaani.org/xz/Doxyfile.in +1234 -0
- data/vendor/git.tukaani.org/xz/INSTALL +618 -0
- data/vendor/git.tukaani.org/xz/INSTALL.generic +365 -0
- data/vendor/git.tukaani.org/xz/Makefile.am +110 -0
- data/vendor/git.tukaani.org/xz/NEWS +571 -0
- data/vendor/git.tukaani.org/xz/PACKAGERS +231 -0
- data/vendor/git.tukaani.org/xz/README +308 -0
- data/vendor/git.tukaani.org/xz/THANKS +124 -0
- data/vendor/git.tukaani.org/xz/TODO +111 -0
- data/vendor/git.tukaani.org/xz/autogen.sh +22 -0
- data/vendor/git.tukaani.org/xz/build-aux/manconv.sh +58 -0
- data/vendor/git.tukaani.org/xz/build-aux/version.sh +24 -0
- data/vendor/git.tukaani.org/xz/configure.ac +900 -0
- data/vendor/git.tukaani.org/xz/debug/Makefile.am +30 -0
- data/vendor/git.tukaani.org/xz/debug/README +17 -0
- data/vendor/git.tukaani.org/xz/debug/crc32.c +39 -0
- data/vendor/git.tukaani.org/xz/debug/full_flush.c +103 -0
- data/vendor/git.tukaani.org/xz/debug/hex2bin.c +53 -0
- data/vendor/git.tukaani.org/xz/debug/known_sizes.c +129 -0
- data/vendor/git.tukaani.org/xz/debug/memusage.c +51 -0
- data/vendor/git.tukaani.org/xz/debug/repeat.c +36 -0
- data/vendor/git.tukaani.org/xz/debug/sync_flush.c +125 -0
- data/vendor/git.tukaani.org/xz/debug/translation.bash +100 -0
- data/vendor/git.tukaani.org/xz/doc/examples/00_README.txt +31 -0
- data/vendor/git.tukaani.org/xz/doc/examples/01_compress_easy.c +297 -0
- data/vendor/git.tukaani.org/xz/doc/examples/02_decompress.c +287 -0
- data/vendor/git.tukaani.org/xz/doc/examples/03_compress_custom.c +193 -0
- data/vendor/git.tukaani.org/xz/doc/examples/04_compress_easy_mt.c +206 -0
- data/vendor/git.tukaani.org/xz/doc/examples/Makefile +24 -0
- data/vendor/git.tukaani.org/xz/doc/examples_old/xz_pipe_comp.c +127 -0
- data/vendor/git.tukaani.org/xz/doc/examples_old/xz_pipe_decomp.c +123 -0
- data/vendor/git.tukaani.org/xz/doc/faq.txt +224 -0
- data/vendor/git.tukaani.org/xz/doc/history.txt +150 -0
- data/vendor/git.tukaani.org/xz/doc/lzma-file-format.txt +166 -0
- data/vendor/git.tukaani.org/xz/doc/xz-file-format.txt +1150 -0
- data/vendor/git.tukaani.org/xz/dos/INSTALL.txt +79 -0
- data/vendor/git.tukaani.org/xz/dos/Makefile +147 -0
- data/vendor/git.tukaani.org/xz/dos/README.txt +123 -0
- data/vendor/git.tukaani.org/xz/dos/config.h +136 -0
- data/vendor/git.tukaani.org/xz/extra/7z2lzma/7z2lzma.bash +115 -0
- data/vendor/git.tukaani.org/xz/extra/scanlzma/scanlzma.c +88 -0
- data/vendor/git.tukaani.org/xz/lib/Makefile.am +32 -0
- data/vendor/git.tukaani.org/xz/lib/getopt.c +1197 -0
- data/vendor/git.tukaani.org/xz/lib/getopt.in.h +226 -0
- data/vendor/git.tukaani.org/xz/lib/getopt1.c +171 -0
- data/vendor/git.tukaani.org/xz/lib/getopt_int.h +131 -0
- data/vendor/git.tukaani.org/xz/m4/.gitignore +38 -0
- data/vendor/git.tukaani.org/xz/m4/ax_check_capsicum.m4 +85 -0
- data/vendor/git.tukaani.org/xz/m4/ax_pthread.m4 +332 -0
- data/vendor/git.tukaani.org/xz/m4/getopt.m4 +71 -0
- data/vendor/git.tukaani.org/xz/m4/posix-shell.m4 +63 -0
- data/vendor/git.tukaani.org/xz/m4/tuklib_common.m4 +22 -0
- data/vendor/git.tukaani.org/xz/m4/tuklib_cpucores.m4 +176 -0
- data/vendor/git.tukaani.org/xz/m4/tuklib_integer.m4 +74 -0
- data/vendor/git.tukaani.org/xz/m4/tuklib_mbstr.m4 +30 -0
- data/vendor/git.tukaani.org/xz/m4/tuklib_physmem.m4 +212 -0
- data/vendor/git.tukaani.org/xz/m4/tuklib_progname.m4 +25 -0
- data/vendor/git.tukaani.org/xz/macosx/build.sh +113 -0
- data/vendor/git.tukaani.org/xz/po/.gitignore +31 -0
- data/vendor/git.tukaani.org/xz/po/LINGUAS +6 -0
- data/vendor/git.tukaani.org/xz/po/Makevars +46 -0
- data/vendor/git.tukaani.org/xz/po/POTFILES.in +13 -0
- data/vendor/git.tukaani.org/xz/po/cs.po +949 -0
- data/vendor/git.tukaani.org/xz/po/de.po +993 -0
- data/vendor/git.tukaani.org/xz/po/fr.po +978 -0
- data/vendor/git.tukaani.org/xz/po/it.po +1067 -0
- data/vendor/git.tukaani.org/xz/po/pl.po +968 -0
- data/vendor/git.tukaani.org/xz/po/vi.po +1039 -0
- data/vendor/git.tukaani.org/xz/src/Makefile.am +42 -0
- data/vendor/git.tukaani.org/xz/src/common/common_w32res.rc +50 -0
- data/vendor/git.tukaani.org/xz/src/common/mythread.h +521 -0
- data/vendor/git.tukaani.org/xz/src/common/sysdefs.h +202 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_common.h +71 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_config.h +7 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_cpucores.c +100 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_cpucores.h +23 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_exit.c +57 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_exit.h +25 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_gettext.h +44 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_integer.h +534 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_mbstr.h +66 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_mbstr_fw.c +31 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_mbstr_width.c +64 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_open_stdxxx.c +57 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_open_stdxxx.h +23 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_physmem.c +216 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_physmem.h +28 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_progname.c +50 -0
- data/vendor/git.tukaani.org/xz/src/common/tuklib_progname.h +32 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/Makefile.am +122 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/Makefile.am +23 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma.h +325 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma/base.h +659 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma/bcj.h +90 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma/block.h +581 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma/check.h +150 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma/container.h +632 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma/delta.h +77 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma/filter.h +425 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma/hardware.h +64 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma/index.h +686 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma/index_hash.h +107 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma/lzma12.h +420 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma/stream_flags.h +223 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma/version.h +121 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/api/lzma/vli.h +166 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/Makefile.inc +53 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/check.c +174 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/check.h +172 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc32_fast.c +82 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc32_small.c +61 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc32_table.c +19 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc32_table_be.h +525 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc32_table_le.h +525 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc32_tablegen.c +117 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc32_x86.S +304 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc64_fast.c +72 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc64_small.c +53 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc64_table.c +19 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc64_table_be.h +521 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc64_table_le.h +521 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc64_tablegen.c +88 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc64_x86.S +287 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/crc_macros.h +30 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/check/sha256.c +196 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/Makefile.inc +79 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/alone_decoder.c +243 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/alone_decoder.h +23 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/alone_encoder.c +163 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/auto_decoder.c +195 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/block_buffer_decoder.c +80 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/block_buffer_encoder.c +337 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/block_buffer_encoder.h +24 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/block_decoder.c +257 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/block_decoder.h +22 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/block_encoder.c +223 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/block_encoder.h +47 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/block_header_decoder.c +124 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/block_header_encoder.c +132 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/block_util.c +90 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/common.c +445 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/common.h +314 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/easy_buffer_encoder.c +27 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/easy_decoder_memusage.c +24 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/easy_encoder.c +24 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/easy_encoder_memusage.c +24 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/easy_preset.c +27 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/easy_preset.h +32 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/filter_buffer_decoder.c +88 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/filter_buffer_encoder.c +55 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/filter_common.c +337 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/filter_common.h +48 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/filter_decoder.c +184 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/filter_decoder.h +23 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/filter_encoder.c +286 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/filter_encoder.h +27 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/filter_flags_decoder.c +46 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/filter_flags_encoder.c +56 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/hardware_cputhreads.c +22 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/hardware_physmem.c +25 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/index.c +1250 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/index.h +73 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/index_decoder.c +352 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/index_encoder.c +256 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/index_encoder.h +23 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/index_hash.c +334 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/memcmplen.h +175 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/outqueue.c +184 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/outqueue.h +156 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/stream_buffer_decoder.c +91 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/stream_buffer_encoder.c +141 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/stream_decoder.c +467 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/stream_decoder.h +22 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/stream_encoder.c +340 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/stream_encoder_mt.c +1143 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/stream_flags_common.c +47 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/stream_flags_common.h +33 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/stream_flags_decoder.c +82 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/stream_flags_encoder.c +86 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/vli_decoder.c +86 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/vli_encoder.c +69 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/common/vli_size.c +30 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/delta/Makefile.inc +23 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/delta/delta_common.c +73 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/delta/delta_common.h +20 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/delta/delta_decoder.c +78 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/delta/delta_decoder.h +26 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/delta/delta_encoder.c +125 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/delta/delta_encoder.h +24 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/delta/delta_private.h +37 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/liblzma.map +108 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/liblzma.pc.in +19 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/liblzma_w32res.rc +12 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lz/Makefile.inc +22 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lz/lz_decoder.c +306 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lz/lz_decoder.h +234 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lz/lz_encoder.c +616 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lz/lz_encoder.h +327 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lz/lz_encoder_hash.h +108 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lz/lz_encoder_hash_table.h +68 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lz/lz_encoder_mf.c +744 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/Makefile.inc +47 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/fastpos.h +141 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/fastpos_table.c +519 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/fastpos_tablegen.c +56 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/lzma2_decoder.c +310 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/lzma2_decoder.h +29 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/lzma2_encoder.c +410 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/lzma2_encoder.h +43 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/lzma_common.h +224 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/lzma_decoder.c +1064 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/lzma_decoder.h +53 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/lzma_encoder.c +677 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/lzma_encoder.h +58 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/lzma_encoder_optimum_fast.c +170 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/lzma_encoder_optimum_normal.c +855 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/lzma_encoder_presets.c +64 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/lzma/lzma_encoder_private.h +148 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/rangecoder/Makefile.inc +21 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/rangecoder/price.h +92 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/rangecoder/price_table.c +22 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/rangecoder/price_tablegen.c +87 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/rangecoder/range_common.h +71 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/rangecoder/range_decoder.h +185 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/rangecoder/range_encoder.h +231 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/simple/Makefile.inc +47 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/simple/arm.c +71 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/simple/armthumb.c +76 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/simple/ia64.c +112 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/simple/powerpc.c +75 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/simple/simple_coder.c +282 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/simple/simple_coder.h +72 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/simple/simple_decoder.c +40 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/simple/simple_decoder.h +22 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/simple/simple_encoder.c +38 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/simple/simple_encoder.h +23 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/simple/simple_private.h +74 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/simple/sparc.c +83 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/simple/x86.c +159 -0
- data/vendor/git.tukaani.org/xz/src/liblzma/validate_map.sh +68 -0
- data/vendor/git.tukaani.org/xz/src/lzmainfo/Makefile.am +39 -0
- data/vendor/git.tukaani.org/xz/src/lzmainfo/lzmainfo.1 +60 -0
- data/vendor/git.tukaani.org/xz/src/lzmainfo/lzmainfo.c +219 -0
- data/vendor/git.tukaani.org/xz/src/lzmainfo/lzmainfo_w32res.rc +12 -0
- data/vendor/git.tukaani.org/xz/src/scripts/Makefile.am +55 -0
- data/vendor/git.tukaani.org/xz/src/scripts/xzdiff.1 +77 -0
- data/vendor/git.tukaani.org/xz/src/scripts/xzdiff.in +200 -0
- data/vendor/git.tukaani.org/xz/src/scripts/xzgrep.1 +98 -0
- data/vendor/git.tukaani.org/xz/src/scripts/xzgrep.in +215 -0
- data/vendor/git.tukaani.org/xz/src/scripts/xzless.1 +69 -0
- data/vendor/git.tukaani.org/xz/src/scripts/xzless.in +58 -0
- data/vendor/git.tukaani.org/xz/src/scripts/xzmore.1 +55 -0
- data/vendor/git.tukaani.org/xz/src/scripts/xzmore.in +78 -0
- data/vendor/git.tukaani.org/xz/src/xz/Makefile.am +111 -0
- data/vendor/git.tukaani.org/xz/src/xz/args.c +700 -0
- data/vendor/git.tukaani.org/xz/src/xz/args.h +44 -0
- data/vendor/git.tukaani.org/xz/src/xz/coder.c +936 -0
- data/vendor/git.tukaani.org/xz/src/xz/coder.h +76 -0
- data/vendor/git.tukaani.org/xz/src/xz/file_io.c +1300 -0
- data/vendor/git.tukaani.org/xz/src/xz/file_io.h +156 -0
- data/vendor/git.tukaani.org/xz/src/xz/hardware.c +150 -0
- data/vendor/git.tukaani.org/xz/src/xz/hardware.h +37 -0
- data/vendor/git.tukaani.org/xz/src/xz/list.c +1192 -0
- data/vendor/git.tukaani.org/xz/src/xz/list.h +18 -0
- data/vendor/git.tukaani.org/xz/src/xz/main.c +330 -0
- data/vendor/git.tukaani.org/xz/src/xz/main.h +30 -0
- data/vendor/git.tukaani.org/xz/src/xz/message.c +1258 -0
- data/vendor/git.tukaani.org/xz/src/xz/message.h +167 -0
- data/vendor/git.tukaani.org/xz/src/xz/mytime.c +89 -0
- data/vendor/git.tukaani.org/xz/src/xz/mytime.h +47 -0
- data/vendor/git.tukaani.org/xz/src/xz/options.c +363 -0
- data/vendor/git.tukaani.org/xz/src/xz/options.h +31 -0
- data/vendor/git.tukaani.org/xz/src/xz/private.h +66 -0
- data/vendor/git.tukaani.org/xz/src/xz/signals.c +209 -0
- data/vendor/git.tukaani.org/xz/src/xz/signals.h +43 -0
- data/vendor/git.tukaani.org/xz/src/xz/suffix.c +399 -0
- data/vendor/git.tukaani.org/xz/src/xz/suffix.h +28 -0
- data/vendor/git.tukaani.org/xz/src/xz/util.c +288 -0
- data/vendor/git.tukaani.org/xz/src/xz/util.h +123 -0
- data/vendor/git.tukaani.org/xz/src/xz/xz.1 +2786 -0
- data/vendor/git.tukaani.org/xz/src/xz/xz_w32res.rc +12 -0
- data/vendor/git.tukaani.org/xz/src/xzdec/Makefile.am +82 -0
- data/vendor/git.tukaani.org/xz/src/xzdec/lzmadec_w32res.rc +12 -0
- data/vendor/git.tukaani.org/xz/src/xzdec/xzdec.1 +146 -0
- data/vendor/git.tukaani.org/xz/src/xzdec/xzdec.c +323 -0
- data/vendor/git.tukaani.org/xz/src/xzdec/xzdec_w32res.rc +12 -0
- data/vendor/git.tukaani.org/xz/tests/Makefile.am +57 -0
- data/vendor/git.tukaani.org/xz/tests/bcj_test.c +65 -0
- data/vendor/git.tukaani.org/xz/tests/compress_prepared_bcj_sparc +0 -0
- data/vendor/git.tukaani.org/xz/tests/compress_prepared_bcj_x86 +0 -0
- data/vendor/git.tukaani.org/xz/tests/create_compress_files.c +158 -0
- data/vendor/git.tukaani.org/xz/tests/files/README +240 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-0-backward_size.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-0-empty-truncated.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-0-footer_magic.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-0-header_magic.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-0-nonempty_index.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-0cat-alone.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-0cat-header_magic.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-0catpad-empty.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-0pad-empty.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-block_header-1.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-block_header-2.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-block_header-3.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-block_header-4.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-block_header-5.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-block_header-6.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-check-crc32.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-check-crc64.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-check-sha256.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-lzma2-1.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-lzma2-2.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-lzma2-3.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-lzma2-4.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-lzma2-5.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-lzma2-6.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-lzma2-7.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-lzma2-8.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-stream_flags-1.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-stream_flags-2.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-stream_flags-3.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-vli-1.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-1-vli-2.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-2-compressed_data_padding.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-2-index-1.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-2-index-2.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-2-index-3.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-2-index-4.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/bad-2-index-5.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-0-empty.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-0cat-empty.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-0catpad-empty.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-0pad-empty.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-3delta-lzma2.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-block_header-1.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-block_header-2.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-block_header-3.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-check-crc32.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-check-crc64.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-check-none.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-check-sha256.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-delta-lzma2.tiff.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-lzma2-1.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-lzma2-2.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-lzma2-3.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-lzma2-4.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-lzma2-5.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-sparc-lzma2.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-1-x86-lzma2.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/good-2-lzma2.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/unsupported-block_header.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/unsupported-check.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/unsupported-filter_flags-1.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/unsupported-filter_flags-2.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/files/unsupported-filter_flags-3.xz +0 -0
- data/vendor/git.tukaani.org/xz/tests/test_bcj_exact_size.c +113 -0
- data/vendor/git.tukaani.org/xz/tests/test_block_header.c +240 -0
- data/vendor/git.tukaani.org/xz/tests/test_check.c +83 -0
- data/vendor/git.tukaani.org/xz/tests/test_compress.sh +142 -0
- data/vendor/git.tukaani.org/xz/tests/test_files.sh +57 -0
- data/vendor/git.tukaani.org/xz/tests/test_filter_flags.c +258 -0
- data/vendor/git.tukaani.org/xz/tests/test_index.c +689 -0
- data/vendor/git.tukaani.org/xz/tests/test_scripts.sh +76 -0
- data/vendor/git.tukaani.org/xz/tests/test_stream_flags.c +180 -0
- data/vendor/git.tukaani.org/xz/tests/tests.h +124 -0
- data/vendor/git.tukaani.org/xz/tests/xzgrep_expected_output +39 -0
- data/vendor/git.tukaani.org/xz/windows/INSTALL-MSVC.txt +47 -0
- data/vendor/git.tukaani.org/xz/windows/INSTALL-MinGW.txt +138 -0
- data/vendor/git.tukaani.org/xz/windows/README-Windows.txt +122 -0
- data/vendor/git.tukaani.org/xz/windows/build.bash +203 -0
- data/vendor/git.tukaani.org/xz/windows/vs2013/config.h +148 -0
- data/vendor/git.tukaani.org/xz/windows/vs2013/liblzma.vcxproj +354 -0
- data/vendor/git.tukaani.org/xz/windows/vs2013/liblzma_dll.vcxproj +383 -0
- data/vendor/git.tukaani.org/xz/windows/vs2013/xz_win.sln +48 -0
- data/vendor/git.tukaani.org/xz/windows/vs2017/config.h +148 -0
- data/vendor/git.tukaani.org/xz/windows/vs2017/liblzma.vcxproj +355 -0
- data/vendor/git.tukaani.org/xz/windows/vs2017/liblzma_dll.vcxproj +384 -0
- data/vendor/git.tukaani.org/xz/windows/vs2017/xz_win.sln +48 -0
- metadata +457 -0
@@ -0,0 +1,224 @@
|
|
1
|
+
|
2
|
+
XZ Utils FAQ
|
3
|
+
============
|
4
|
+
|
5
|
+
Q: What do the letters XZ mean?
|
6
|
+
|
7
|
+
A: Nothing. They are just two letters, which come from the file format
|
8
|
+
suffix .xz. The .xz suffix was selected, because it seemed to be
|
9
|
+
pretty much unused. It has no deeper meaning.
|
10
|
+
|
11
|
+
|
12
|
+
Q: What are LZMA and LZMA2?
|
13
|
+
|
14
|
+
A: LZMA stands for Lempel-Ziv-Markov chain-Algorithm. It is the name
|
15
|
+
of the compression algorithm designed by Igor Pavlov for 7-Zip.
|
16
|
+
LZMA is based on LZ77 and range encoding.
|
17
|
+
|
18
|
+
LZMA2 is an updated version of the original LZMA to fix a couple of
|
19
|
+
practical issues. In context of XZ Utils, LZMA is called LZMA1 to
|
20
|
+
emphasize that LZMA is not the same thing as LZMA2. LZMA2 is the
|
21
|
+
primary compression algorithm in the .xz file format.
|
22
|
+
|
23
|
+
|
24
|
+
Q: There are many LZMA related projects. How does XZ Utils relate to them?
|
25
|
+
|
26
|
+
A: 7-Zip and LZMA SDK are the original projects. LZMA SDK is roughly
|
27
|
+
a subset of the 7-Zip source tree.
|
28
|
+
|
29
|
+
p7zip is 7-Zip's command-line tools ported to POSIX-like systems.
|
30
|
+
|
31
|
+
LZMA Utils provide a gzip-like lzma tool for POSIX-like systems.
|
32
|
+
LZMA Utils are based on LZMA SDK. XZ Utils are the successor to
|
33
|
+
LZMA Utils.
|
34
|
+
|
35
|
+
There are several other projects using LZMA. Most are more or less
|
36
|
+
based on LZMA SDK. See <http://7-zip.org/links.html>.
|
37
|
+
|
38
|
+
|
39
|
+
Q: Why is liblzma named liblzma if its primary file format is .xz?
|
40
|
+
Shouldn't it be e.g. libxz?
|
41
|
+
|
42
|
+
A: When the designing of the .xz format began, the idea was to replace
|
43
|
+
the .lzma format and use the same .lzma suffix. It would have been
|
44
|
+
quite OK to reuse the suffix when there were very few .lzma files
|
45
|
+
around. However, the old .lzma format became popular before the
|
46
|
+
new format was finished. The new format was renamed to .xz but the
|
47
|
+
name of liblzma wasn't changed.
|
48
|
+
|
49
|
+
|
50
|
+
Q: Do XZ Utils support the .7z format?
|
51
|
+
|
52
|
+
A: No. Use 7-Zip (Windows) or p7zip (POSIX-like systems) to handle .7z
|
53
|
+
files.
|
54
|
+
|
55
|
+
|
56
|
+
Q: I have many .tar.7z files. Can I convert them to .tar.xz without
|
57
|
+
spending hours recompressing the data?
|
58
|
+
|
59
|
+
A: In the "extra" directory, there is a script named 7z2lzma.bash which
|
60
|
+
is able to convert some .7z files to the .lzma format (not .xz). It
|
61
|
+
needs the 7za (or 7z) command from p7zip. The script may silently
|
62
|
+
produce corrupt output if certain assumptions are not met, so
|
63
|
+
decompress the resulting .lzma file and compare it against the
|
64
|
+
original before deleting the original file!
|
65
|
+
|
66
|
+
|
67
|
+
Q: I have many .lzma files. Can I quickly convert them to the .xz format?
|
68
|
+
|
69
|
+
A: For now, no. Since XZ Utils supports the .lzma format, it's usually
|
70
|
+
not too bad to keep the old files in the old format. If you want to
|
71
|
+
do the conversion anyway, you need to decompress the .lzma files and
|
72
|
+
then recompress to the .xz format.
|
73
|
+
|
74
|
+
Technically, there is a way to make the conversion relatively fast
|
75
|
+
(roughly twice the time that normal decompression takes). Writing
|
76
|
+
such a tool would take quite a bit of time though, and would probably
|
77
|
+
be useful to only a few people. If you really want such a conversion
|
78
|
+
tool, contact Lasse Collin and offer some money.
|
79
|
+
|
80
|
+
|
81
|
+
Q: I have installed xz, but my tar doesn't recognize .tar.xz files.
|
82
|
+
How can I extract .tar.xz files?
|
83
|
+
|
84
|
+
A: xz -dc foo.tar.xz | tar xf -
|
85
|
+
|
86
|
+
|
87
|
+
Q: Can I recover parts of a broken .xz file (e.g. a corrupted CD-R)?
|
88
|
+
|
89
|
+
A: It may be possible if the file consists of multiple blocks, which
|
90
|
+
typically is not the case if the file was created in single-threaded
|
91
|
+
mode. There is no recovery program yet.
|
92
|
+
|
93
|
+
|
94
|
+
Q: Is (some part of) XZ Utils patented?
|
95
|
+
|
96
|
+
A: Lasse Collin is not aware of any patents that could affect XZ Utils.
|
97
|
+
However, due to the nature of software patents, it's not possible to
|
98
|
+
guarantee that XZ Utils isn't affected by any third party patent(s).
|
99
|
+
|
100
|
+
|
101
|
+
Q: Where can I find documentation about the file format and algorithms?
|
102
|
+
|
103
|
+
A: The .xz format is documented in xz-file-format.txt. It is a container
|
104
|
+
format only, and doesn't include descriptions of any non-trivial
|
105
|
+
filters.
|
106
|
+
|
107
|
+
Documenting LZMA and LZMA2 is planned, but for now, there is no other
|
108
|
+
documentation than the source code. Before you begin, you should know
|
109
|
+
the basics of LZ77 and range-coding algorithms. LZMA is based on LZ77,
|
110
|
+
but LZMA is a lot more complex. Range coding is used to compress
|
111
|
+
the final bitstream like Huffman coding is used in Deflate.
|
112
|
+
|
113
|
+
|
114
|
+
Q: I cannot find BCJ and BCJ2 filters. Don't they exist in liblzma?
|
115
|
+
|
116
|
+
A: BCJ filter is called "x86" in liblzma. BCJ2 is not included,
|
117
|
+
because it requires using more than one encoded output stream.
|
118
|
+
A streamable version of BCJ2-style filtering is planned.
|
119
|
+
|
120
|
+
|
121
|
+
Q: I need to use a script that runs "xz -9". On a system with 256 MiB
|
122
|
+
of RAM, xz says that it cannot allocate memory. Can I make the
|
123
|
+
script work without modifying it?
|
124
|
+
|
125
|
+
A: Set a default memory usage limit for compression. You can do it e.g.
|
126
|
+
in a shell initialization script such as ~/.bashrc or /etc/profile:
|
127
|
+
|
128
|
+
XZ_DEFAULTS=--memlimit-compress=150MiB
|
129
|
+
export XZ_DEFAULTS
|
130
|
+
|
131
|
+
xz will then scale the compression settings down so that the given
|
132
|
+
memory usage limit is not reached. This way xz shouldn't run out
|
133
|
+
of memory.
|
134
|
+
|
135
|
+
Check also that memory-related resource limits are high enough.
|
136
|
+
On most systems, "ulimit -a" will show the current resource limits.
|
137
|
+
|
138
|
+
|
139
|
+
Q: How do I create files that can be decompressed with XZ Embedded?
|
140
|
+
|
141
|
+
A: See the documentation in XZ Embedded. In short, something like
|
142
|
+
this is a good start:
|
143
|
+
|
144
|
+
xz --check=crc32 --lzma2=preset=6e,dict=64KiB
|
145
|
+
|
146
|
+
Or if a BCJ filter is needed too, e.g. if compressing
|
147
|
+
a kernel image for PowerPC:
|
148
|
+
|
149
|
+
xz --check=crc32 --powerpc --lzma2=preset=6e,dict=64KiB
|
150
|
+
|
151
|
+
Adjust the dictionary size to get a good compromise between
|
152
|
+
compression ratio and decompressor memory usage. Note that
|
153
|
+
in single-call decompression mode of XZ Embedded, a big
|
154
|
+
dictionary doesn't increase memory usage.
|
155
|
+
|
156
|
+
|
157
|
+
Q: Will xz support threaded compression?
|
158
|
+
|
159
|
+
A: It is planned and has been taken into account when designing
|
160
|
+
the .xz file format. Eventually there will probably be three types
|
161
|
+
of threading, each method having its own advantages and disadvantages.
|
162
|
+
|
163
|
+
The simplest method is splitting the uncompressed data into blocks
|
164
|
+
and compressing them in parallel independent from each other.
|
165
|
+
Since the blocks are compressed independently, they can also be
|
166
|
+
decompressed independently. Together with the index feature in .xz,
|
167
|
+
this allows using threads to create .xz files for random-access
|
168
|
+
reading. This also makes threaded decompression possible, although
|
169
|
+
it is not clear if threaded decompression will ever be implemented.
|
170
|
+
|
171
|
+
The independent blocks method has a couple of disadvantages too. It
|
172
|
+
will compress worse than a single-block method. Often the difference
|
173
|
+
is not too big (maybe 1-2 %) but sometimes it can be too big. Also,
|
174
|
+
the memory usage of the compressor increases linearly when adding
|
175
|
+
threads.
|
176
|
+
|
177
|
+
Match finder parallelization is another threading method. It has
|
178
|
+
been in 7-Zip for ages. It doesn't affect compression ratio or
|
179
|
+
memory usage significantly. Among the three threading methods, only
|
180
|
+
this is useful when compressing small files (files that are not
|
181
|
+
significantly bigger than the dictionary). Unfortunately this method
|
182
|
+
scales only to about two CPU cores.
|
183
|
+
|
184
|
+
The third method is pigz-style threading (I use that name, because
|
185
|
+
pigz <http://www.zlib.net/pigz/> uses that method). It doesn't
|
186
|
+
affect compression ratio significantly and scales to many cores.
|
187
|
+
The memory usage scales linearly when threads are added. This isn't
|
188
|
+
significant with pigz, because Deflate uses only a 32 KiB dictionary,
|
189
|
+
but with LZMA2 the memory usage will increase dramatically just like
|
190
|
+
with the independent-blocks method. There is also a constant
|
191
|
+
computational overhead, which may make pigz-method a bit dull on
|
192
|
+
dual-core compared to the parallel match finder method, but with more
|
193
|
+
cores the overhead is not a big deal anymore.
|
194
|
+
|
195
|
+
Combining the threading methods will be possible and also useful.
|
196
|
+
E.g. combining match finder parallelization with pigz-style threading
|
197
|
+
can cut the memory usage by 50 %.
|
198
|
+
|
199
|
+
It is possible that the single-threaded method will be modified to
|
200
|
+
create files identical to the pigz-style method. We'll see once
|
201
|
+
pigz-style threading has been implemented in liblzma.
|
202
|
+
|
203
|
+
|
204
|
+
Q: How do I build a program that needs liblzmadec (lzmadec.h)?
|
205
|
+
|
206
|
+
A: liblzmadec is part of LZMA Utils. XZ Utils has liblzma, but no
|
207
|
+
liblzmadec. The code using liblzmadec should be ported to use
|
208
|
+
liblzma instead. If you cannot or don't want to do that, download
|
209
|
+
LZMA Utils from <https://tukaani.org/lzma/>.
|
210
|
+
|
211
|
+
|
212
|
+
Q: The default build of liblzma is too big. How can I make it smaller?
|
213
|
+
|
214
|
+
A: Give --enable-small to the configure script. Use also appropriate
|
215
|
+
--enable or --disable options to include only those filter encoders
|
216
|
+
and decoders and integrity checks that you actually need. Use
|
217
|
+
CFLAGS=-Os (with GCC) or equivalent to tell your compiler to optimize
|
218
|
+
for size. See INSTALL for information about configure options.
|
219
|
+
|
220
|
+
If the result is still too big, take a look at XZ Embedded. It is
|
221
|
+
a separate project, which provides a limited but significantly
|
222
|
+
smaller XZ decoder implementation than XZ Utils. You can find it
|
223
|
+
at <https://tukaani.org/xz/embedded.html>.
|
224
|
+
|
@@ -0,0 +1,150 @@
|
|
1
|
+
|
2
|
+
History of LZMA Utils and XZ Utils
|
3
|
+
==================================
|
4
|
+
|
5
|
+
Tukaani distribution
|
6
|
+
|
7
|
+
In 2005, there was a small group working on the Tukaani distribution,
|
8
|
+
which was a Slackware fork. One of the project's goals was to fit the
|
9
|
+
distro on a single 700 MiB ISO-9660 image. Using LZMA instead of gzip
|
10
|
+
helped a lot. Roughly speaking, one could fit data that took 1000 MiB
|
11
|
+
in gzipped form into 700 MiB with LZMA. Naturally, the compression
|
12
|
+
ratio varied across packages, but this was what we got on average.
|
13
|
+
|
14
|
+
Slackware packages have traditionally had .tgz as the filename suffix,
|
15
|
+
which is an abbreviation of .tar.gz. A logical naming for LZMA
|
16
|
+
compressed packages was .tlz, being an abbreviation of .tar.lzma.
|
17
|
+
|
18
|
+
At the end of the year 2007, there was no distribution under the
|
19
|
+
Tukaani project anymore, but development of LZMA Utils was kept going.
|
20
|
+
Still, there were .tlz packages around, because at least Vector Linux
|
21
|
+
(a Slackware based distribution) used LZMA for its packages.
|
22
|
+
|
23
|
+
First versions of the modified pkgtools used the LZMA_Alone tool from
|
24
|
+
Igor Pavlov's LZMA SDK as is. It was fine, because users wouldn't need
|
25
|
+
to interact with LZMA_Alone directly. But people soon wanted to use
|
26
|
+
LZMA for other files too, and the interface of LZMA_Alone wasn't
|
27
|
+
comfortable for those used to gzip and bzip2.
|
28
|
+
|
29
|
+
|
30
|
+
First steps of LZMA Utils
|
31
|
+
|
32
|
+
The first version of LZMA Utils (4.22.0) included a shell script called
|
33
|
+
lzmash. It was a wrapper that had a gzip-like command-line interface. It
|
34
|
+
used the LZMA_Alone tool from LZMA SDK to do all the real work. zgrep,
|
35
|
+
zdiff, and related scripts from gzip were adapted to work with LZMA and
|
36
|
+
were part of the first LZMA Utils release too.
|
37
|
+
|
38
|
+
LZMA Utils 4.22.0 included also lzmadec, which was a small (less than
|
39
|
+
10 KiB) decoder-only command-line tool. It was written on top of the
|
40
|
+
decoder-only C code found from the LZMA SDK. lzmadec was convenient in
|
41
|
+
situations where LZMA_Alone (a few hundred KiB) would be too big.
|
42
|
+
|
43
|
+
lzmash and lzmadec were written by Lasse Collin.
|
44
|
+
|
45
|
+
|
46
|
+
Second generation
|
47
|
+
|
48
|
+
The lzmash script was an ugly and not very secure hack. The last
|
49
|
+
version of LZMA Utils to use lzmash was 4.27.1.
|
50
|
+
|
51
|
+
LZMA Utils 4.32.0beta1 introduced a new lzma command-line tool written
|
52
|
+
by Ville Koskinen. It was written in C++, and used the encoder and
|
53
|
+
decoder from C++ LZMA SDK with some little modifications. This tool
|
54
|
+
replaced both the lzmash script and the LZMA_Alone command-line tool
|
55
|
+
in LZMA Utils.
|
56
|
+
|
57
|
+
Introducing this new tool caused some temporary incompatibilities,
|
58
|
+
because the LZMA_Alone executable was simply named lzma like the new
|
59
|
+
command-line tool, but they had a completely different command-line
|
60
|
+
interface. The file format was still the same.
|
61
|
+
|
62
|
+
Lasse wrote liblzmadec, which was a small decoder-only library based
|
63
|
+
on the C code found from LZMA SDK. liblzmadec had an API similar to
|
64
|
+
zlib, although there were some significant differences, which made it
|
65
|
+
non-trivial to use it in some applications designed for zlib and
|
66
|
+
libbzip2.
|
67
|
+
|
68
|
+
The lzmadec command-line tool was converted to use liblzmadec.
|
69
|
+
|
70
|
+
Alexandre Sauvé helped converting the build system to use GNU
|
71
|
+
Autotools. This made it easier to test for certain less portable
|
72
|
+
features needed by the new command-line tool.
|
73
|
+
|
74
|
+
Since the new command-line tool never got completely finished (for
|
75
|
+
example, it didn't support the LZMA_OPT environment variable), the
|
76
|
+
intent was to not call 4.32.x stable. Similarly, liblzmadec wasn't
|
77
|
+
polished, but appeared to work well enough, so some people started
|
78
|
+
using it too.
|
79
|
+
|
80
|
+
Because the development of the third generation of LZMA Utils was
|
81
|
+
delayed considerably (3-4 years), the 4.32.x branch had to be kept
|
82
|
+
maintained. It got some bug fixes now and then, and finally it was
|
83
|
+
decided to call it stable, although most of the missing features were
|
84
|
+
never added.
|
85
|
+
|
86
|
+
|
87
|
+
File format problems
|
88
|
+
|
89
|
+
The file format used by LZMA_Alone was primitive. It was designed with
|
90
|
+
embedded systems in mind, and thus provided only a minimal set of
|
91
|
+
features. The two biggest problems for non-embedded use were the lack
|
92
|
+
of magic bytes and an integrity check.
|
93
|
+
|
94
|
+
Igor and Lasse started developing a new file format with some help
|
95
|
+
from Ville Koskinen. Also Mark Adler, Mikko Pouru, H. Peter Anvin,
|
96
|
+
and Lars Wirzenius helped with some minor things at some point of the
|
97
|
+
development. Designing the new format took quite a long time (actually,
|
98
|
+
too long a time would be a more appropriate expression). It was mostly
|
99
|
+
because Lasse was quite slow at getting things done due to personal
|
100
|
+
reasons.
|
101
|
+
|
102
|
+
Originally the new format was supposed to use the same .lzma suffix
|
103
|
+
that was already used by the old file format. Switching to the new
|
104
|
+
format wouldn't have caused much trouble when the old format wasn't
|
105
|
+
used by many people. But since the development of the new format took
|
106
|
+
such a long time, the old format got quite popular, and it was decided
|
107
|
+
that the new file format must use a different suffix.
|
108
|
+
|
109
|
+
It was decided to use .xz as the suffix of the new file format. The
|
110
|
+
first stable .xz file format specification was finally released in
|
111
|
+
December 2008. In addition to fixing the most obvious problems of
|
112
|
+
the old .lzma format, the .xz format added some new features like
|
113
|
+
support for multiple filters (compression algorithms), filter chaining
|
114
|
+
(like piping on the command line), and limited random-access reading.
|
115
|
+
|
116
|
+
Currently the primary compression algorithm used in .xz is LZMA2.
|
117
|
+
It is an extension on top of the original LZMA to fix some practical
|
118
|
+
problems: LZMA2 adds support for flushing the encoder, uncompressed
|
119
|
+
chunks, eases stateful decoder implementations, and improves support
|
120
|
+
for multithreading. Since LZMA2 is better than the original LZMA, the
|
121
|
+
original LZMA is not supported in .xz.
|
122
|
+
|
123
|
+
|
124
|
+
Transition to XZ Utils
|
125
|
+
|
126
|
+
The early versions of XZ Utils were called LZMA Utils. The first
|
127
|
+
releases were 4.42.0alphas. They dropped the rest of the C++ LZMA SDK.
|
128
|
+
The code was still directly based on LZMA SDK but ported to C and
|
129
|
+
converted from a callback API to a stateful API. Later, Igor Pavlov
|
130
|
+
made a C version of the LZMA encoder too; these ports from C++ to C
|
131
|
+
were independent in LZMA SDK and LZMA Utils.
|
132
|
+
|
133
|
+
The core of the new LZMA Utils was liblzma, a compression library with
|
134
|
+
a zlib-like API. liblzma supported both the old and new file format.
|
135
|
+
The gzip-like lzma command-line tool was rewritten to use liblzma.
|
136
|
+
|
137
|
+
The new LZMA Utils code base was renamed to XZ Utils when the name
|
138
|
+
of the new file format had been decided. The liblzma compression
|
139
|
+
library retained its name though, because changing it would have
|
140
|
+
caused unnecessary breakage in applications already using the early
|
141
|
+
liblzma snapshots.
|
142
|
+
|
143
|
+
The xz command-line tool can emulate the gzip-like lzma tool by
|
144
|
+
creating appropriate symlinks (e.g. lzma -> xz). Thus, practically
|
145
|
+
all scripts using the lzma tool from LZMA Utils will work as is with
|
146
|
+
XZ Utils (and will keep using the old .lzma format). Still, the .lzma
|
147
|
+
format is more or less deprecated. XZ Utils will keep supporting it,
|
148
|
+
but new applications should use the .xz format, and migrating old
|
149
|
+
applications to .xz is often a good idea too.
|
150
|
+
|
@@ -0,0 +1,166 @@
|
|
1
|
+
|
2
|
+
The .lzma File Format
|
3
|
+
=====================
|
4
|
+
|
5
|
+
0. Preface
|
6
|
+
0.1. Notices and Acknowledgements
|
7
|
+
0.2. Changes
|
8
|
+
1. File Format
|
9
|
+
1.1. Header
|
10
|
+
1.1.1. Properties
|
11
|
+
1.1.2. Dictionary Size
|
12
|
+
1.1.3. Uncompressed Size
|
13
|
+
1.2. LZMA Compressed Data
|
14
|
+
2. References
|
15
|
+
|
16
|
+
|
17
|
+
0. Preface
|
18
|
+
|
19
|
+
This document describes the .lzma file format, which is
|
20
|
+
sometimes also called LZMA_Alone format. It is a legacy file
|
21
|
+
format, which is being or has been replaced by the .xz format.
|
22
|
+
The MIME type of the .lzma format is `application/x-lzma'.
|
23
|
+
|
24
|
+
The most commonly used software to handle .lzma files are
|
25
|
+
LZMA SDK, LZMA Utils, 7-Zip, and XZ Utils. This document
|
26
|
+
describes some of the differences between these implementations
|
27
|
+
and gives hints what subset of the .lzma format is the most
|
28
|
+
portable.
|
29
|
+
|
30
|
+
|
31
|
+
0.1. Notices and Acknowledgements
|
32
|
+
|
33
|
+
This file format was designed by Igor Pavlov for use in
|
34
|
+
LZMA SDK. This document was written by Lasse Collin
|
35
|
+
<lasse.collin@tukaani.org> using the documentation found
|
36
|
+
from the LZMA SDK.
|
37
|
+
|
38
|
+
This document has been put into the public domain.
|
39
|
+
|
40
|
+
|
41
|
+
0.2. Changes
|
42
|
+
|
43
|
+
Last modified: 2011-04-12 11:55+0300
|
44
|
+
|
45
|
+
|
46
|
+
1. File Format
|
47
|
+
|
48
|
+
+-+-+-+-+-+-+-+-+-+-+-+-+-+==========================+
|
49
|
+
| Header | LZMA Compressed Data |
|
50
|
+
+-+-+-+-+-+-+-+-+-+-+-+-+-+==========================+
|
51
|
+
|
52
|
+
The .lzma format file consist of 13-byte Header followed by
|
53
|
+
the LZMA Compressed Data.
|
54
|
+
|
55
|
+
Unlike the .gz, .bz2, and .xz formats, it is not possible to
|
56
|
+
concatenate multiple .lzma files as is and expect the
|
57
|
+
decompression tool to decode the resulting file as if it were
|
58
|
+
a single .lzma file.
|
59
|
+
|
60
|
+
For example, the command line tools from LZMA Utils and
|
61
|
+
LZMA SDK silently ignore all the data after the first .lzma
|
62
|
+
stream. In contrast, the command line tool from XZ Utils
|
63
|
+
considers the .lzma file to be corrupt if there is data after
|
64
|
+
the first .lzma stream.
|
65
|
+
|
66
|
+
|
67
|
+
1.1. Header
|
68
|
+
|
69
|
+
+------------+----+----+----+----+--+--+--+--+--+--+--+--+
|
70
|
+
| Properties | Dictionary Size | Uncompressed Size |
|
71
|
+
+------------+----+----+----+----+--+--+--+--+--+--+--+--+
|
72
|
+
|
73
|
+
|
74
|
+
1.1.1. Properties
|
75
|
+
|
76
|
+
The Properties field contains three properties. An abbreviation
|
77
|
+
is given in parentheses, followed by the value range of the
|
78
|
+
property. The field consists of
|
79
|
+
|
80
|
+
1) the number of literal context bits (lc, [0, 8]);
|
81
|
+
2) the number of literal position bits (lp, [0, 4]); and
|
82
|
+
3) the number of position bits (pb, [0, 4]).
|
83
|
+
|
84
|
+
The properties are encoded using the following formula:
|
85
|
+
|
86
|
+
Properties = (pb * 5 + lp) * 9 + lc
|
87
|
+
|
88
|
+
The following C code illustrates a straightforward way to
|
89
|
+
decode the Properties field:
|
90
|
+
|
91
|
+
uint8_t lc, lp, pb;
|
92
|
+
uint8_t prop = get_lzma_properties();
|
93
|
+
if (prop > (4 * 5 + 4) * 9 + 8)
|
94
|
+
return LZMA_PROPERTIES_ERROR;
|
95
|
+
|
96
|
+
pb = prop / (9 * 5);
|
97
|
+
prop -= pb * 9 * 5;
|
98
|
+
lp = prop / 9;
|
99
|
+
lc = prop - lp * 9;
|
100
|
+
|
101
|
+
XZ Utils has an additional requirement: lc + lp <= 4. Files
|
102
|
+
which don't follow this requirement cannot be decompressed
|
103
|
+
with XZ Utils. Usually this isn't a problem since the most
|
104
|
+
common lc/lp/pb values are 3/0/2. It is the only lc/lp/pb
|
105
|
+
combination that the files created by LZMA Utils can have,
|
106
|
+
but LZMA Utils can decompress files with any lc/lp/pb.
|
107
|
+
|
108
|
+
|
109
|
+
1.1.2. Dictionary Size
|
110
|
+
|
111
|
+
Dictionary Size is stored as an unsigned 32-bit little endian
|
112
|
+
integer. Any 32-bit value is possible, but for maximum
|
113
|
+
portability, only sizes of 2^n and 2^n + 2^(n-1) should be
|
114
|
+
used.
|
115
|
+
|
116
|
+
LZMA Utils creates only files with dictionary size 2^n,
|
117
|
+
16 <= n <= 25. LZMA Utils can decompress files with any
|
118
|
+
dictionary size.
|
119
|
+
|
120
|
+
XZ Utils creates and decompresses .lzma files only with
|
121
|
+
dictionary sizes 2^n and 2^n + 2^(n-1). If some other
|
122
|
+
dictionary size is specified when compressing, the value
|
123
|
+
stored in the Dictionary Size field is a rounded up, but the
|
124
|
+
specified value is still used in the actual compression code.
|
125
|
+
|
126
|
+
|
127
|
+
1.1.3. Uncompressed Size
|
128
|
+
|
129
|
+
Uncompressed Size is stored as unsigned 64-bit little endian
|
130
|
+
integer. A special value of 0xFFFF_FFFF_FFFF_FFFF indicates
|
131
|
+
that Uncompressed Size is unknown. End of Payload Marker (*)
|
132
|
+
is used if and only if Uncompressed Size is unknown.
|
133
|
+
|
134
|
+
XZ Utils rejects files whose Uncompressed Size field specifies
|
135
|
+
a known size that is 256 GiB or more. This is to reject false
|
136
|
+
positives when trying to guess if the input file is in the
|
137
|
+
.lzma format. When Uncompressed Size is unknown, there is no
|
138
|
+
limit for the uncompressed size of the file.
|
139
|
+
|
140
|
+
(*) Some tools use the term End of Stream (EOS) marker
|
141
|
+
instead of End of Payload Marker.
|
142
|
+
|
143
|
+
|
144
|
+
1.2. LZMA Compressed Data
|
145
|
+
|
146
|
+
Detailed description of the format of this field is out of
|
147
|
+
scope of this document.
|
148
|
+
|
149
|
+
|
150
|
+
2. References
|
151
|
+
|
152
|
+
LZMA SDK - The original LZMA implementation
|
153
|
+
http://7-zip.org/sdk.html
|
154
|
+
|
155
|
+
7-Zip
|
156
|
+
http://7-zip.org/
|
157
|
+
|
158
|
+
LZMA Utils - LZMA adapted to POSIX-like systems
|
159
|
+
http://tukaani.org/lzma/
|
160
|
+
|
161
|
+
XZ Utils - The next generation of LZMA Utils
|
162
|
+
http://tukaani.org/xz/
|
163
|
+
|
164
|
+
The .xz file format - The successor of the .lzma format
|
165
|
+
http://tukaani.org/xz/xz-file-format.txt
|
166
|
+
|