On 5/10/22 13:14, Panu Matilainen wrote:
On 5/10/22 12:13, Neal H. Walfield wrote:
Hi libtool devs,
Historically, rpm has included its own OpenPGP implementation. This
implementation is incomplete and buggy, and the maintainers of rpm
have decided that they would like to use a different OpenPGP
implementation.
There are two major constraints. Because rpm's OpenPGP API is public,
it must be preserved until the next soname bump. And, the OpenPGP
backend should be pluggable.
[...]
My conclusion is that I somehow need to get librpmio to reexport
librpm_sequoia's symbols. Despite spending hours searching, I haven't
figured out how to do that. I'd appreciate any hints that might lead
me to a solution.
The simple and straightforward solution is to leave the rpm API into
librpmio, and use a separate one for the PGP backend. Ie the backend
implements an API which librpmio calls, and therefore we have the right
dependencies automatically.
That's how the crypto backend between openssl and gnutls works, and
ditto with rpmdb backend. Runtime swappable can be handy for testing,
but maybe not worth here.
Or in other words: what in the world is not solvable by adding another
layer of indirection? :D
- Panu -
