[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnu-arch-users] Re: [ANNOUNCEMENT] /Arch/ embraces `git'

From: Szilard Hajba
Subject: [Gnu-arch-users] Re: [ANNOUNCEMENT] /Arch/ embraces `git'
Date: Thu, 21 Apr 2005 12:18:48 +0200
User-agent: Mutt/1.5.6+20040907i

On Wed, Apr 20, 2005 at 02:32:29PM -0700, Tom Lord wrote:
> My understanding is still superficial in that detail:  I gather that
> zip formats are standardized by a IETF document.  I am not certain
> that the spec implies deterministic output.   I am not certain that
> the way I'm driving `libz', so as to be compatible with Linus' code,
> is the right way to do it.


Some compressions are really standardized, but this doesn't guarantees that
the compressed files are the same. The standards define some methods for
uncompressing, but does not define how to get the compressed form.

Let's define a 'standard' compressed format like this:


This character sequence:   "aaaaaabbbbbccccccdddddddddddddddddddd"
Can be written as compressed: "{a,6}{b,5}{c,6}{d,20}"

But the following string is also suitable:
Can be written as compressed: "{a,6}{b,5}{c,6}{d,5}{d,5}{d,5}{d,5}"

Tha standard defines a format and the uncompression methods. But the way I gat
to the compressed file is not defined. Compression programs are evoluting
slowly, the generated output is better and better, but the underling standard,
the file format is the same.

Of course it is possible to make such a compression standard that defines
exact compressed data, but then further developments are disabled, so it is
not a good thing.


Szilard Hajba                   Symbion Ltd.
Phone:  (+36)20/203-31-56       H-9028 Gyor, Uj u. 38.
ICQ:    12892911                E-Mail: address@hidden
Skype:  hszilu

reply via email to

[Prev in Thread] Current Thread [Next in Thread]