On Tue 2020-01-28 13:01:04 +0100, Francois Gouget wrote: > The only blocker for making libgpg-error-dev Multi-Arch: same is > gpg-error-config. However gpg-error-config is not needed on Debian > since there is no need for -I or -L directives; and it has been > superseded by gpgrt-config and pkgconfig anyway. > > So I think it is reasonable to stop shipping gpg-error-config, just like > FreeType stopped shipping freetype-config to become multiarch-compatible.
I agree that upstream's preferred configuration mechanism
(gpg-error-config) is not well-suited for the modern multiarch world.
That said, I'm not convinced that removal of upstream's preferred
configuration mechanism in debian is a great idea. Have you
successfully built (for example) libgcrypt or the other reverse
dependencies in debian against such a modified package?
> libgcrypt is under consideration for use in Wine but Wine depends on
> proper multiarch support since we need to support both 32 bit and 64 bit
> Windows applications (even 64 bit Windows applications have 32 bit
> installers).
What other encryption libraries has Wine considered for the purposes it
is considering libgcrypt for? Nettle should have comparable licensing
concerns, a similar spread of cryptographic primitives covered, and a
more idiomatic C interface (algortihm-specific structs, no
S-expression string management, etc)
--dkg
signature.asc
Description: PGP signature
