There are reasons that the krb5 upstream build does not include static libs.
The main problem is that more and more krb5 depends on plugins for various things. As an example, preauthentication, KDC location,' GSS-API mechanisms all support plugins. In the krb5 in wheezy, you cannot request FAST credentials in some realms without plugin support. I think it's a different set of things that fail in krb5 1.11, but generally you cannot assume that a static build of krb5 will provide acceptable functionality for general use. The reason the upstream build system supports static is because for certain test coverage analysis gcc works a lot better with static objects. So, I'm open to including static support in a special package (not libkrb5-dev), but I'd need to understand the use case and be convinced it's actually a good idea. Like the curl maintainer I'm very uncomfortable producing builds that have a different set of functionality between static and dynamic. However it's more or less inherently true that will be the case for krb5. --Sam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
