Re: kerberos is the new sqlite: disable, force mit, or ?

[Greg Troxel <gdt%lexort.com@localhost>]

Taylor R Campbell <riastradh%NetBSD.org@localhost> writes:

> I looked closer and it occurs to me that, pending any implementation
> of new machinery for this, we could fix postgresql16 by changing:
>
> -.  include "../../security/mit-krb5/buildlink3.mk"
> +KRB5_ACCEPTED=		mit-krb5
> +.  include "../../mk/krb5.buildlink3.mk"
>
> I will commit this today if there are no objections.

I think that's totally fine (assuming postgresql16 builds after your
change :-).

I don't see how it addresses the problem I raised.  In the default build
(which is what official bulk builds must do), postgresql16 will use
mit-krb5, curl will use base heimdal, and any program that links with
both libcurl and libpq will explode.

> It looks like we have exactly two other direct users of mit-krb5
> buildlink3.mk (other than security/mit-krb5-appl) which should maybe
> get the same treatment if they really need mit-krb5:
>
> comms/kermit
> www/lighttpd

agreed it is reasonable for someone(tm) to look into that, validate that
things work with heimdal, and make it generic if so.