Hello, Let me explain that what direction we should go.
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. True. Since 1.33, libgpg-error have distributed new libgpg-error/src/gpg-error.m4 which can be used with no gpg-error-config (but gpgrt-config). In other cases, software which builds with pkgconfig just uses gpg-error.pc directly. My intention of keeping gpg-error-config is to support existing system which depends on old behavior. New gpgrt-config requires POSIX compatible Borne shell and I was afraid that there are still some OSes without POSIX compatible Borne shell, so, it still distributes the old gpg-error-config. Daniel Kahn Gillmor <d...@fifthhorseman.net> wrote: > I agree that upstream's preferred configuration mechanism > (gpg-error-config) is not well-suited for the modern multiarch world. gpg-error-config is shipped for backword compatibility. When there will be no packages which use gpg-error-config, it could be removed or for system with POSIX compatible Borne shell, it could be replaced by gpgrt-config (symbolic link to gpgrt-config) if needed. In future release of libgpg-error, gpg-error-config will be a symbolic link to gpgrt-config at installation (when detected POSIX compatible Borne shell, or we will ignore system with no POSIX compatible Borne shell). --