On Thu, Jul 19, 2007 at 11:02:39AM -0700, Russ Allbery wrote: > Now, I'm willing to lead the way for Kerberos packages going forward, I > guess, if I can figure out a good way to do that, but I don't know how > that configure logic would even work or what those --with flags would look > like. The problem would be avoided if I required krb5-config be > available, but I don't really want to do that, both because older versions > of Kerberos don't have it and because krb5-config adds a bunch of needless > shared library dependencies that create unnecessary interpackage > dependencies in Debian.
Ideally everything should use libgssapi2 (or some other mechglue implementation) and nothing should build directly aginst the Kerberos-specific GSSAPI implementations. That would allow users to select at run-time between different Kerberos versions or use other GSSAPI implementations. It would also solve the dependency problems you mentioned. The only question is how hard it would be to make Heimdal work with libgssapi2. I know there was some mechglue-related work in Heimdal but I did not follow that. Gabor -- --------------------------------------------------------- MTA SZTAKI Computer and Automation Research Institute Hungarian Academy of Sciences --------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]