[832] in Kerberos_V5_Development
Re: rearranging krb5 include files: please retain some sanity
daemon@ATHENA.MIT.EDU (Theodore Ts'o)
Mon Jan 23 10:16:17 1995
Date: Mon, 23 Jan 1995 10:16:11 +0500
From: Theodore Ts'o <tytso@MIT.EDU>
To: John Kohl <jtk@atria.com>
Cc: krbdev@MIT.EDU, proven@MIT.EDU, eichin@cygnus.com
In-Reply-To: John Kohl's message of Sun, 22 Jan 1995 17:23:38 -0500,
<199501222223.RAA00132@singha.atria.com>
The basic idea which we're looking at is that what you export out to an
application writer will be a *single* krb5.h file. Hence, it can live
up in the top-level. During the build process, the krb5.h file will be
constructed from a number of subsidiary files that will remain in
src/include/krb5.h, but the expectation is that we won't actually need
to install any of the files in src/include.
I expect that if a vendor ships Kerberos V5 bundled, it will install
krb5.h in /usr/include, or perhaps in /usr/local/include.
Does this still give you heartburn? If so, why?
- Ted
