Merged #910 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/910#event-2735844957___
Rpm-maint mailing list
Conan-Kudo approved this pull request.
--
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/910#pullrequestreview-305582921___
> Make database backends self-aware
:cold_sweat:
--
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/910#issuecomment-544540645___
Rebased and added both rpmdbStat() and rpmdbFStat() now.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
mlschroe approved this pull request.
--
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/910#pullrequestreview-304543216___
Okay okay, maybe not...
Add name and path members to backend db_ops struct, use them for configuring
and detecting, and misc related tweaks.
Started doing this for implementing rpmdbStat(), but got stuck wondering about
the API: my initial version requires an open rpmdb for stating, which
