[Rpm-maint] [rpm-software-management/rpm] Add an API for libsolv, libdnf, et al to use to check if rpmdb has changed and trivially get path to rpmdb (#388)

[Neal Gompa (ニール・ゴンパ)]

Quoted from @pmatilai in https://github.com/rpm-software-management/libdnf/issues/362#issuecomment-341325991:
> Of course, libdnf is not poking at rpmdb directory just for fun, it does it to see if the rpmdb was changed since the last time. That information is something that librpm should be providing via an API. And now that this came up, I remember going through this same discussion at least twice before in the last 8-9 years but nothing ever got implemented in rpm, so my bad I guess :-/

Also quoted from @pmatilai in https://github.com/rpm-software-management/libdnf/issues/362#issuecomment-341325991:
> AFAICS libdnf does this to see if there is a valid rpmdb cache it can use, which seems fairly reasonable as such, but then libsolv also has similar logic in it. So there's probably something else to streamline etc besides rpm needing to add that rpmdb cookie API.

I'm currently beginning experiments with non-BDB rpmdb, but these assumptions made about how the rpmdb exists causes problems, as I need to patch them to "know" the alternative paths used by the different backends.

It'd be nice if there was a nice backend-agnostic set of APIs to solve these problems in libsolv, libdnf, and dnf so that this stops being a problem and even as more backends and changes to existing ones occur, everything won't break.

-- 
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/issues/388
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20180201/30a83402/attachment.html>