I have heimdal kerberos 5 emerged that satisfies: virtual/krb5 app-crypt/heimdal emergeing cyrus-sasl-2.1.14 afterward with USE="kerberos" causes mit-krb5 to trample the heimdal install. I know cyrus-sasl works with heimdal but the ebuild breaks it. My solution is to unemerge mit-krb5 and reemerge heimdal after cyrus-sasl is emerged.
RedDog, which versions of mit-krb5 and heimdal are you working with here? As of mit-krb5-1.3.1-r1.ebuild (marked stable), mit-krb5 properly blocks any other virtual/krb5's. Also, heimdal-0.6.2.ebuild (also stable) properly blocks any other virtual/krb5's. Are you working with these versions, but still experiencing clobbering? Finally, does cyrus-sasl work with the heimdal kerberos libraries? If so, we could make cyrus-sasl depend on virtual/krb5 instead of mit-krb5 specifically. Thanks for your help!
No response to ping. Close as NEEDINFO.