--n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 29, 2003 at 11:50:25AM -0400, Michael Stenner wrote: > Regarding gzip and timestamps: >=20 > On Mon, Apr 28, 2003 at 10:54:05PM -0400, seth vidal wrote: > > it can be and if it can be done nicely in the code I will, but I don't > > think it can be done that cleanly at the moment. >=20 > I talked with seth about this a little. It is possible to do this in > the yum code, but not cleanly. The added complexity is probably not > worth the modest benefit. In case it's useful to anyone, I'm > including a file that subclasses the gzip stuff and writes files with > a null timestamp. >=20 > I'm also including a short script which nulls the timestamps in > existing gzip files. You should be able to do a=20 > =20 > null_gzip_ts.py *.hdr >=20 > In your headers dir after each rebuild. (there may be buffer length > issues requiring you do for file in *.hdr; do null_gzip_ts.py $file; > done) Thank you, I took the null_gzip_ts.py and now zero the timestamps after each yum-arch. I already had a directory comparison tool, which sets the oldest timestamp for identical files, so in combination I managed to have my hdr files stop changing (contents and modification time wise), which makes cach= es, rsync and logs happy (me, too ;). I wish that yum-arch could do that without a workaround, of course, e.g. timestamping the hdr files (both internally in the gzip header and the file itself) with the timestamp of the originating rpm. yum-arch could even= use this to not bother extracting the header out of an rpm, if the corresponding hdr file with the right timestamp exists (the evr is encoded in the name anyway). But that's only a wish, I am also happy with the workaround. Did I mention I was happy? ;) --=20 Axel.Thimm@xxxxxxxxxxxxxxxxxxx --n8g4imXOkfNTN/H1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+rvdnQBVS1GOamfERAv1/AJ95JZrpplKZ0Ux6CVWYucxmTPSlaACfWZiv Gg1OG1zWIxUBQHLO2wUFXy0= =0buc -----END PGP SIGNATURE----- --n8g4imXOkfNTN/H1--
