Unfortunately, krb5-config is used fairly widely by software not in Debian. In the past krb5 has been fairly conservative, which in this case would mean having krb5-multidev depend on krb5-multidev-bin for a release. If we did that we would have a solution for buster+1 to make krb5-multidev m-a installable.
Obviously we could be less conservative here. I'd rather find a more clever solution. Is there any way to map back from CC to something useful as an installation architecture? I'd prefer something that worked both for gcc and llvm. My hope is to do something like * install krb5-config.mit * have that be a script that calls krb5-config.mit.tripple * Each package only includes krb5-config.mit.tripple for the appropriate architecture. If we can make that work, does that make people happy? Do we have any thoughts on how to make that work?
