Mail Archives: djgpp/2017/02/12/14:07:05
This is a port of clzip 1.8 to MSDOS/DJGPP.
clzip is a lossless data compressor with a user interface similar to the one
of gzip or bzip2. Clzip is about as fast as gzip, compresses most files more
than bzip2, and is better than both from a data recovery perspective.
DJGPP specific changes.
=======================
- The port implements SFN support in a similar manner than it has been
done for the bzip2 and xz ports. If only SFN support is available the
file name and its extension must be truncated and modified to encode the
compressor extension and the numbers to identify a multi volume archive.
The program does not store the original file name in the header of the
archive thus there is no chance to regenerate them when uncompressiong
the archive in a SFN environment. Here the same naming schema than used
in the bzip2 and xz ports is applied. The archiver extension is ".lz".
On SFN systems, the ".lz" extension will consume one or two characters
of the original file name extension.
For SFN systems the following rules apply for ".lz" extension:
compressed name uncompressed name
filename.exl --> filename.ex
filename.elz --> filename.e
filename.lz --> filename
uncompressed name compressed name
filename.ext --> filename.exl
filename.ex --> filename.exl
filename.e --> filename.elz
filename --> filename.lz
The port will detect at run time if LFN support is available or not and
will select the method to handle the extension creation accordingly.
For LFN and SFN systems, the ".tlz" extension will always be identified
as tar archives. Their file name will always have a ".tar" extension.
If only SFN support is available, the DJGPP port of clzip will always
consume the last 5 characters of the 8 possible name characters to
encode the volume number. E.g.: when compressing a file with the file
name filename.ext and splitting it into multiple volumes, the different
volumes will become fil00001.exl, fil00002.exl, etc. It is clear that
neither the original filename nor the original extension can be recreated.
- LFN support enabled is required to run the testsuite. The test data is
binary data thus the used unzip program must treat them as binary and
not as text data.
- The port has been configured and compiled on WinXP SP3 and Win98SE.
There is no guarantee that this may be possible with any other DOS-like
OS. Due to the massive use of long file names it will not be possible
to configure and compile without LFN support.
To build this port you will need an OS with LFN support to configure and
compile the source package.
As usual, all djgpp specific files (diffs, README files, etc.) are stored in
the /djgpp directory. The sources have been configured to be build in the
"_build" directory. If for some reason it does not work for you, delete it
contents and configure from scratch again.
For further information about clzip please read the info docs and NEWS file.
This is a verbatim extract of the NEWS file:
-------------------------------------------------------------------------------
It is the first DJGPP port of clzip. Read the complete NEWS file.
-------------------------------------------------------------------------------
The port consists of the usual three packages produced using djdev205
that can be downloaded from ftp.delorie.com and mirrors as (time stamp 2017-02-11):
clzip 1.8 binary and info format documentation:
ftp://ftp.delorie.com/pub/djgpp/current/v2apps/clzp18b.zip
clzip 1.8 dvi, html, ps and pdf format documentation:
ftp://ftp.delorie.com/pub/djgpp/current/v2apps/clzp18d.zip
clzip 1.8 source:
ftp://ftp.delorie.com/pub/djgpp/current/v2apps/clzp18s.zip
Send clzip specific bug reports to <lzip-bug@@nongnu.org>.
Send suggestions and bug reports concerning the DJGPP port to
comp.os.msdos.djgpp or <djgpp AT delorie DOT com>.
Enjoy.
Guerrero, Juan Manuel <juan DOT guerrero AT gmx DOT de>
- Raw text -