[Yum] Re: Recreating headers yields different files

[Axel Thimm]

On Mon, Apr 28, 2003 at 04:58:40PM -0400, seth vidal wrote:
> > it uses the current time. If you ask google for
> > http://www.google.com/search?q=gzip+modification+time
> > you get as the first document
> > http://www.ietf.org/rfc/rfc1952.txt
> > which describes the gzip format:
> 
> Right, so I looked at the gzip module in python and the zlib module and
> I came shockingly to the conclusion that controlling or disabling time
> stamping on the gzip call is not possible in those libraries.

Maybe writing first the file, timestamping it and then gzipping it?

> having said that for 1.7GB worth of distro data the headers occupy 17M.
> Not exactly a heavy load for an rsyncing host.
> less than 2s at 100Mbps

That's correct, only that you need to pull all of these 17MB each time
anything changed (like adding a new package, which for my repo has a mean size
of 1.3MB). Even so, it isn't that critical, I just thought I spotted something
that can be optimized (thinking here more of web caching than rsyncing).
-- 
Axel.Thimm at physik.fu-berlin.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.baseurl.org/pipermail/yum/attachments/20030429/7a2006f3/attachment-0001.pgp