On Sat, 13 Feb 2010, Satish Eerpini wrote:
Hello everyone,
we were looking at a particular scenario when yum-presto plugin is
installed. If the number of package updates (or the size of the
package updates) during a particular update is low, it so happens that
the prestodelta metadata is much higher in size than the actual
package updates.
I tried to introduce a checkpoint in the presto code, so that the size
of the metadata and the size of the actual package updates to be
downloaded are compared, and in case the prestodelta metadata is
larger in size, presto is skipped and normal package update happens.
Being a novice at this myself, I referred the scenario to the presto
people and I was told that currently the size of the prestodelta
metadata cannot be known before downloading it. And to be able to know
the delta download size, the repomd.xml needs to store the size
information also.
Please let me know what are the possibilities.
size info is already in repomd.xml
here's a prestodelta stanza:
<data type="prestodelta">
<checksum
type="sha256">a0563080b67b12ca27c6e2b7b8247c1500b409f067fd4801fe895bceed6830f8</checksum>
<timestamp>1266073226</timestamp>
<size>105728</size>
<open-size>488612</open-size>
<open-checksum
type="sha256">587646c420b6d46f80db6cd6472b5f22802874709da20d45f8552bf022b4e169</open-checksum>
<location href="repodata/prestodelta.xml.gz"/>
-sv
size == compressed size
open-size == decompressed size
-sv
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxx
http://lists.baseurl.org/mailman/listinfo/yum
