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 |
||
---|---|---|
.. | ||
fetch-journal.sh | ||
install.sh | ||
multitest.py | ||
overlay.sh | ||
sync.sh | ||
test-basic.sh | ||
test-download-only.sh | ||
test-initramfs.sh | ||
test-kernel-args.sh | ||
test-layering-basic.sh | ||
test-layering-gpg.sh | ||
test-layering-local.sh | ||
test-layering-non-root-caps.sh | ||
test-layering-relabel.sh | ||
test-layering-relayer.sh | ||
test-layering-rpmdb.sh | ||
test-layering-scripts.sh | ||
test-layering-unified.sh | ||
test-livefs.sh | ||
test-override-local-replace.sh | ||
test-override-remove.sh | ||
test.sh |