…nged
Add rpmdbCookie() public function and matching python bindings.
The returned value is an opaque string which changes any time the rpmdb
is changed (eg packages added or removed, rebuild changes things etc).
A key point is that this is entirely database backend agnostic.
The actual implement
This assumes that the iterator always returns the entries in the same order,
which might not be true for some db implementations (randomization as a
security feature). But feel free to ignore this for now ;)
--
You are receiving this because you are subscribed to this thread.
Reply to this emai
We can always have an optional per-db cookie implementation if it becomes
necessary. It's not like the cookie needs to be consistent across different
implementations, it's merely handy if it can be implemented that way.
In the meanwhile, I realized this version is quite flawed as it just hashes
Pushed an update which hashes the package offsets per each key as is necessary
for correct operation in various cases - add test for that too.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-m
Pushed an update to make rpmdbIndexIteratorPkgOffsets() const correct while at
it.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/712#issuecomment-496101946___
Merged #712 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/712#event-2369355438___
Rpm-maint mailing list
Rpm-maint
