[947] in arla-drinkers
Re: whining about roken.h
daemon@ATHENA.MIT.EDU (Jeffrey Hutzelman)
Wed Jul 7 17:52:07 1999
From owner-arla-drinkers@stacken.kth.se Wed Jul 07 21:52:07 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 16492 invoked from network); 7 Jul 1999 21:52:06 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 7 Jul 1999 21:52:06 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id XAA29409
for arla-drinkers-list; Wed, 7 Jul 1999 23:45:20 +0200 (MET DST)
Received: from minbar.fac.cs.cmu.edu (MINBAR.FAC.CS.CMU.EDU [128.2.185.161])
by sundance.stacken.kth.se (8.8.8/8.8.8) with SMTP id XAA29405
for <arla-drinkers@stacken.kth.se>; Wed, 7 Jul 1999 23:45:14 +0200 (MET DST)
Received: from AFSTEST-2.FAC.CS.CMU.EDU by minbar.fac.cs.cmu.edu id aa08281;
7 Jul 99 17:45 EDT
Date: Wed, 07 Jul 1999 17:43:14 -0400
From: Jeffrey Hutzelman <jhutz+@cmu.edu>
To: Assar Westerlund <assar@sics.se>
cc: arla-drinkers@stacken.kth.se
Subject: Re: whining about roken.h
Message-ID: <3656458314.931369394@AFSTEST-2.FAC.CS.CMU.EDU>
In-Reply-To: <5lbtdob3ep.fsf@assaris.sics.se>
Originator-Info: login-token=Mulberry:01ab54gNMm7fS1CfcDrkDp4vQj5K2rNwDf7NvzaSz0CWkx3vE=;
token_authority=postmaster@andrew.cmu.edu
X-Mailer: Mulberry (Win32) [1.4.1, s/n S-100002]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
On Wednesday, July 07, 1999, 10:39 PM +0200 Assar Westerlund
<assar@sics.se> wrote:
> As Johan already said, the roken being used in krb4/heimdal does
> exactly this for exactly the reasons you said. And it's mostly my
> fault that these features haven't been merged in Arla's roken. I've
> been working on merging the different strains of roken, but the real
> plan looks something like:
>
> a. do a separate roken distribution (with its own version number)
> b. include it in the required programs
> c. have configure check for an existing roken and if it's of the
> required version. otherwise, build the included roken and install it.
Yes; that sounds entirely reasonable. I'm also considering putting
together a separate distribution containing lwp, rx, dx, and the various
support things they need. Obviously I can't usefully include rxkad, but
perhaps if I put together a coherent distribution then KTH will pick it up,
add rxkad, and distribute and maintain it...
-- Jeff
