[617] in Kerberos-V5-bugs
Re: Kerberos 5 on SunOS 4.1.3.
daemon@ATHENA.MIT.EDU ("Mark W. Eichin")
Tue Aug 2 18:44:58 1994
Date: Tue, 2 Aug 94 18:35:34 EDT
From: eichin@MIT.EDU ("Mark W. Eichin")
To: adrian@ada1.elan.af.mil (L. Adrian Griffis)
Cc: Tom Yu <tlyu@MIT.EDU>, adrian@ada1.elan.af.mil (L. Adrian
Griffis),
krb5-bugs@MIT.EDU, adrian@ada1.elan.af.mil
In-Reply-To: "[616] in Kerberos-V5-bugs"
>> I'd like to do it in such a way that you can incorporate my changes
>> back into your release. Is that idea of interrest to you folks at MIT?
If you could send your patches to krb5-bugs, that'd be great... I'll
certainly be testing autoconfiguration on Irix 5.2, but possibly not
before the next snapshot.
>> If there are any notes about the portability strategy that you've
1) Code for POSIX, then implement fixes for things that aren't
2) Test features, not attitudes -- specifically, autoconf should be
able to identify a feature (and possibly test if it works) and then
have the source code test for the HAVE_feature flag. Checking for
defines like BSD or __svr4__ is generally wrong.
2a) Try to make feature tests that work at compile-time, and don't
need to run anything -- they're usually faster, and they will work in
a cross-compilation environment...
3) Don't look at appl/bsd or appl/telnet until the next snapshot :-)
These are just what come to mind from discussions that Tom, Ted, and I
have had; I don't think we've ever written them up as strategy before.
_Mark_ <eichin@athena.mit.edu>
MIT Student Information Processing Board
Cygnus Support <eichin@cygnus.com>
