Hi Florian,
On Tue, 10 May 2022 12:04:52 +0200,
Florian Weimer wrote:
> * Neal H. Walfield:
>
> > 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 plu
On Tue, 10 May 2022 12:48:23 +0200,
Florian Weimer wrote:
> * Neal H. Walfield:
> > On Tue, 10 May 2022 12:04:52 +0200,
> > Florian Weimer wrote:
> >> * Neal H. Walfield:
> >>
> >> > There are two major constraints. Because rpm's OpenPGP API is
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 publ