IMO, it should be distributed with it and referenced
in a new README.kaserver (which also should include
the elders EOL statement regarding kaserver).
It doesn't have to be referenced by the build process.
I wouldn't surprise me to find that nobody agrees with
me again.
Jeffrey Altman wrote:
Derrick Brashear wrote:
On 10/25/07, *Jeff Blaine* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
You had me wondering.
The only reference to afs2k5db I could find in source was
src/packaging/RedHat/openafs.spec.in
Which then leads me to:
Are the RedHat builds getting preferential treatment with
regard to this? Is there a reason? What's up?
in the sense that warlord made the rpms ship the entire afs-krb5 kit,
and no other set of packages does, yes.
technically that wasn't part of openafs. i think it's in 1.4.5 now though.
afs2k5db is not part of openafs 1.4.5. Building it requires access to
private MIT krb5 headers. We would distribute it if we could build it
using the public headers but we can't.
Jeffrey Altman
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
