Thanks. I'll take a look next week. This looks very promising. Unless I'm missing something, I think you've done a lot of the work regardless of whether we want to wrap krb5-config architecture scripts or wrap a script that calls cross-pkg-config.
Why do you want to replace krb5-config with pkg-config? That seems like a good option if we can sell upstream on the idea, but something requiring more thought otherwise. Are there advantages/simplicities in coding that led you to that approach? I'd like to understand so I can evaluate. less good options i'm a bit concerned that getting the behavior of all the different --libs options for the different types of Kerberos apps will be a bit fiddly.
