As per summary, libassuan installs only .a (archive, static) libraries, rather than shared objects. This is usually against policy; even if the usage of static library is reasoned, there are packages depending on libassuan at runtime, but being only static, they should only depend on it at build time: [18:54] <Flameeyes> !rrdep libassuan [18:54] <jeeves> dev-libs/libassuan <- app-crypt/dirmngr app-crypt/gnupg app-crypt/gnupg-pkcs11-scd HTH, Diego
There was a discussion of this in upstream. Thread at: http://lists.gnupg.org/pipermail/gnupg-devel/2006-December/023462.html What do you recommend to do?
Debian has a policy much similar to us, so I'd say follow whatever they are doing; in this case, they are not using a shared library either, so until libassuan devs release something that is stable and supported as shared object, libassuan should be moved from RDEPEND to DEPEND.
Fixed. Done waiting. Thanks.