|
From: | Antonio Diaz Diaz |
Subject: | Re: ChangeLog encoding; testsuite file/s |
Date: | Tue, 18 Jan 2022 00:03:28 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 |
Adam Tuja wrote:
BTW, the development version of gzip generates and compresses a file of 4 GiB of uncompressed size to test the new functionality of --list because it is the smallest file able to test it.Looks like you have answered yourself to this - they can be generated, as in gzip example you gave.
Some can be generated, others can't (or it is more complicated to generate them than to include them in the tarball). Size is not the only important feature of a test file. Moreover, lzip's test script already generates a good number of test files on the fly using as building blocks the test files that you want to replace.
I will prepare script later, when have more time.
I don't know what problem you are trying to solve, but it surely can't be an excessive size of the lzip source tarball because it is in fact pretty small:
-rw-r--r-- 1 772666 Dec 30 2018 gzip-1.10.tar.lz -rw-r--r-- 1 83501 Nov 30 20:15 lzip-1.23-rc1.tar.lz Best regards, Antonio.
[Prev in Thread] | Current Thread | [Next in Thread] |