Currently with keepAfterInstall=1, up2date keeps *everything*, not just RPM packages. However it seems silly and unnecessary to keep the .hdr packages, even when keepAfterInstall=1
hmm, indeed. I'll see if I can fix that in the next version.
Plea for the opposite: caching the .hdr "packages" is quite important when a) you have a slow or busy connection, b) the up2date server(s) have a slow (congested) connection, and/or c) there are quite a few of them. Perhaps a setting on how many to keep, like a maximum cache size?
Right now .hde packages are *never* reused, even when kept. If you think they should be, you should probably file a different RFE for that. We could do something like keepAfterInstall=0 => nothing kept keepAfterInstall=1 => only RPMs are kept keepAfterInstall=2 => both RPMs and .hdr are kept (files like redhat-linux-i386-7.2.20011031233847 should still be removed). OTOH, I don't think it's worth keeping .hdr when .rpm is already there! It would probably be a better idea if up2date could just skip .hdr download and use .rpm for queries when .rpm is already there (the added bonus is that it's simple to check that the .rpm is authentic by using the GPG sig, but it's harder to check the authenticity of an existing .hdr).
ayn2: I think you are wrong, up2date does use the already saved .hdr instead of re-downloading them. And yes, if up2date does find the rpm, it will use it instead of the header. This is true for Red Hat 7.2 up2date, not sure about previous versions
left over .hdr file could be used, but then, if you already downloaded the .hdr, then the package, and installed the package, you shouldnt ever need the hdr again (the same info should now be in the rpm database). If only the rpms are available (either in /var/spool/up2date, or in a path specified via -d) up2date will read the header from the local rpm instead of downloading the remote header again. There isnt really any need to keep the .hdr files around after the app is finished. The fact they arent deleted is probabaly a bug. (need to reverify that that doesnt break anything, but I'm pretty sure it doesnt).
It appears that even when both .rpm and .hdr are there, up2date still re-downloads the .hdr (at least the timestamp of the .hdr changes).
> And yes, if up2date does find the rpm, it will use it instead of the header. Just tried it with latest up2date (up2date-2.7.11-7.x.2), it still re-creates .hdr even when the .rpm are present.
2 plus years old. Closing. Reopen if there is an issue over this.