Benjamin Kaduk <ka...@mit.edu> writes: > On Mon, Nov 13, 2017 at 10:51:10AM -0800, Russ Allbery wrote:
>> I'm not sure how best to fix this other than no longer using >> krb5-config and shipping a pkgconfig script or something. One could >> move the krb5-config script into an architecture-specific directory, >> but that just moves the problem to a different area (how to find the >> right krb5-config script to use). > Upstream started shipping a pkgconfig script a couple releases ago. I > forget whether we do and/or need to patch it to match our configuration. That's great news and is probably the best path going forward. pkgconfig is really the correct solution to this problem (or as close to correct as the C build ecosystem has today). Unfortunately, it's also a transition for everything else that links against Kerberos libraries, and the sort of transition that will probably never be finished. :( For instance, several of my orphaned Kerberos packages, for which I don't intend to make another release, rely on krb5-config and don't know about the pkgconfig approach to finding Kerberos libraries. That said, Debian could decide to just only support pkgconfig and not krb5-config. I'm not sure how disruptive of a change that would be. Or put krb5-config into a separate package that's not multiarch. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
