Seems to work, but API usage is pretty limited so I might just have tested
the bits that are used :).
We now store these rpmdb/yumdb entries in the history DB, mainly when the
package is installed (in verifyTransaction()):
rpmdb:
_valid_rpmdb_keys = set(["buildtime", "buildhost",
"license", "packager",
"size", "sourcerpm", "url", "vendor",
# ?
"committer", "committime"])
yumdb:
_valid_yumdb_keys = set(["command_line",
"from_repo", "from_repo_revision",
"from_repo_timestamp",
"installed_by", "changed_by",
"reason", "releasever"])
...I'm pretty sure the yumdb keys are "complete", less so about the rpmdb
ones. Esp. it might be more useful to store pacakgesize, or both.
We don't store summary or description, the former _might_ be useful the
later hopefully not.
Rough stats. are that my history DB went from ~125k to ~425k when I ran
"yum history sync".
Schema is probably the simplest possible, just text key/val pairs tied
to the pkgtupid. Should be able to drop the size by having a text=>num
table for the keys ... not sure it's worth it though.
Questions/Discussion?
_______________________________________________
Yum-devel mailing list
[email protected]
http://lists.baseurl.org/mailman/listinfo/yum-devel
