Profile include support

[Russ Allbery]

Ken Raeburn <raeburn at MIT.EDU> writes:

> Russ is right, this should be fixed, whether as part of this project or
> separately.  But if krb5_init_context can fail because of a profile
> library error, it becomes difficult to pass the error back to the
> application, even with profile library API changes.  If we can go
> config-file-free (I forget, did that ever get fully implemented?), then
> certainly the krb5_context can hold the profile library error info.

It's incredibly ugly, I know, but if krb5_get_error_message(NULL, code)
returned an appropriate error message after krb5_init_context failed, my
existing code at least would happily retrieve it and report that error.
You'd have to do something nasty with library globals in order to
implement that, though.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>