On 2007-01-02 Nathanael Nerode <[EMAIL PROTECTED]> wrote: > Package: libgcrypt11-dev > Severity: wishlist
> Currently libgcrypt11-dev ships with a "libgcrypt-config" which > causes trouble for Debian. It spreads unnecessary > dependencies on libgpg-error0 all the way up the dependency chain > to every package which uses it. > While this is basically a bug in each of those packages (they shouldn't > be using libgcrypt-config), it is rather tedious to fix it in all > those packages, because the fixes cannot go upstream. Hello, I will go the same way as with libgnutls and simply patch libgcrypt-config to output just -lgcrypt on --libs. > If libgcrypt11-dev used pkg-config with Libs.private (or provided a > libgcrypt-config which understood shared libraries), then the other > packages could switch to using pkg-config for libgcrypt, a change > which *could* go upstream. > For background, see http://rerun.lefant.net/checklib/ . > If libgpg-error ever changes soname, there will be a world of hurt > for transitions to testing, and it's all caused by libgcrypt-config. FWIW that is rather unlikely event. http://lists.gnupg.org/pipermail/gnupg-devel/2004-March/020851.html cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
