d9e870be88
The new `rpmdb.pkglist` metadata is a cheap way of retrieving the set of packages in a commit. I'd like to make use of it as much as possible vs. checking out the rpmdb and setting up a DnfSack. Of course, in the case of layered commits, it doesn't matter *as* much, because a layered commit being present in the repo should mean that a deployment is currently using it, and we should learn to reuse the rpmdb checkout of that deployment. Though keeping it consistent across both server and client commits makes implementing `OstreeDeployment`-agnostic things like `db diff` more efficient too. I also plan to use this in the upcoming auto-update code. Closes: #1158 Approved by: cgwalters |
||
---|---|---|
.. | ||
libbasic-test.sh | ||
libcomposetest.sh | ||
test-basic-unified.sh | ||
test-basic.sh | ||
test-boot-location-new.sh | ||
test-install-langs.sh | ||
test-installroot.sh | ||
test-jigdo.sh | ||
test-misc-tweaks.sh | ||
test-mutate-os-release.sh |