Connect Swdb with DNF and document exposed API. * Swdb is redesigned and merged history db and yumdb. It's a standalone library with C/C++/Python API that will be used by Dnf/PackageKit/yum to maintain log of transaction and additional package info (from which repo was package installed, reason, group info, etc.).
I don't think this is a good idea to add such functionality at this level. You should add an API for storing such information to rpm. rpm itself can then use swdb for storage.
This goal was suspended for a while. We can reconsider the layers.
*** Bug 1227949 has been marked as a duplicate of this bug. ***
Pardon my lack of knowledge here. But what is swdb and where to find more information about it ? How's this related to yumdb stored informations ?
*** Bug 1276850 has been marked as a duplicate of this bug. ***
*** Bug 1276921 has been marked as a duplicate of this bug. ***
Could we please see this implemented? The inconsistency between PackageKit based frontends and DNF is maddening!
This will not be implemented anytime soon. We should reuse functions of libhif in DNF at first then by the needs implement the swdb. When PK write to dnfdb then it will be fine (bug 1259865).
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Now that DNF is going to be using libhif with DNF 2.0, what's the status on unifying the transactional information recording between PK and DNF?
update: there are the PRs in progress: https://github.com/rpm-software-management/libdnf/pull/199 https://github.com/rpm-software-management/dnf/pull/630
*** Bug 1430269 has been marked as a duplicate of this bug. ***
Fixed as part of dnf-3.0 and libdnf-0.14 in upstream. They will be released soon.