[Yum-devel] delta metadata index file & dbversion change

[James Bowes]

On Wed, Jun 27, 2007 at 07:34:59AM -0400, seth vidal wrote:
> Will the database actually be incompatible with the older clients? It
> seems like we'd just be generating a changeset that should cleanly
> modify the database and results in a db in a format identical to what
> we're now using. Did I read this wrong?

Your reading skills are fine; I didn't explain myself well enough. :)

So after applying the deltas, the db will be usable by older clients.
The difference is that the new format has a new entry for revision/id,
similar to the dbversion entry.

The current dbversion is 10. We'll say the new dbversion including the
revision field is 10.1. yum-3.2.1 can read dbversion 10, and should have
no problems reading dbversion 10.1, but the code we have now will say
there is a dbversion mismatch, and regenerate the db. Instead, it should
happily use version 10.1 while ignoring the new info.

yum-3.whatever can read dbversion 10.1, but dbversion 10 is missing the
revision info, so it cannot effectively use dbversion 10 (well, it
could, without the delta stuff, but that's probably not a case we're
concerned with. Instead yum can see if the delta xml stuff exists or
not).

Instead, we could just skip this altogether and store the revision/id
info outside of the sqlite files, but I still feel there could be some
use to the dbversion minor number.

-James
-------------- 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-devel/attachments/20070627/25edd5d7/attachment.pgp