Subject: re: krb5 integration proposal
To: Aidan Cully <aidan@kublai.com>
From: matthew green <mrg@eterna.com.au>
List: current-users
Date: 06/09/1999 11:58:48
   
   1) Move all exportable code and headers out of /usr/src/domestic.
   	compile_et
   	limcom_err
   	mk_cmds
   	libdyn


i assume you mean moving these to the master repository?  unless you
can provide an convincing argument that these are genuinely useful
beyond their needs for kerberos, _please_ don't do this.


also, don't you mean to use `crypto-us' not `domestic' ?  it would be
helpful to use the new terminology :-)

   	Perhaps this directory should be domestic/dist/krb5?

using a `dist' strategy would be winning.

   6) Make krb4 a package (to help with people upgrading from k4, at least..)

shouldn't you do this first, really, before breaking anything? :-)

   Stuff that looks troublesome:
   GSSRPC.  On Ken Hornstein's advice, I've given up trying to merge libc's
   rpc implementation with krb5's gssrpc implementation..  There will be two
   RPC libraries installed on the system. (one of which is libc.)

this is a large pity.



.mrg.