Closed #289.
--
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/289#event-1800025450___
Rpm-maint mailing list
Rpm-maint@lists.rpm
FWIW, there are other markups that could be usefully added to rpmdb, like CUDF
(or other SAT solver inputs).
The real issue is compatibility with commonly used external tools, not so much
whether the output markup is implemented in an existing rpmdb executable or a
separate ndb_dump utility.
-
Bundling into rpmdb would be fine: just there needs to be a common interchange
format. E.g. libvirt uses db_dump and is opposed to NDB because it lacks an
equivalent. The textual non-hex format is occasionally useful as well (but with
digests/signatures one cannot just edit the database).
--
Y
Wouldn't it be better if rpmdb gets dump/load/stat options?
--
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/289#issuecomment-319025432_
Converting databases is painful, particularly if both forward/backward
conversions are desired.
BerkeleyDB has a set of utilities to do this conversion, LMDB uses an almost
identical set of utilities.
While rpmdb --importdb/--exportdb are a high performing KISS improvement on
the BDB-style du
