curl +krb4 automatically pulls in kth-krb, while I think that mit-krb5 with +krb4 would be a valid way to satisfy the dependency. note that kerberos depends on virtual/krb5 which can be satisfied with mit-krb5. I'd supply a patch, but I don't know how to express the dependency of "mit-krb5 compiled with +krb4"
(In reply to comment #0) > I'd supply a patch, but I don't know how to express the dependency of "mit-krb5 > compiled with +krb4" There's no way to express such dependency (yet). *** This bug has been marked as a duplicate of 2272 ***
(In reply to comment #1) > (In reply to comment #0) > > I'd supply a patch, but I don't know how to express the dependency of "mit-krb5 > > compiled with +krb4" > > There's no way to express such dependency (yet). Well, it could be done how e.g. evolution does it, i.e. depend on virtual/krb5 (and in this case || kth-krb) and if mit-krb5 is detected, fail if kth-krb is not around and it wasn't compiled with krb4. But really it would be ideal if this could be done directly as a dependency.
