[128] in Athena User Interface
Re: RFC: Prioritized AUI component list
daemon@ATHENA.MIT.EDU (Thomas Bushnell, BSG)
Tue Jun 6 13:25:37 2000
To: Richard Tibbetts <tibbetts@MIT.EDU>
Cc: Maciej Stachowiak <mjs@eazel.com>, BSG@MIT.EDU, Bill Cattey <wdc@MIT.EDU>,
"Christopher D. Beland" <beland@MIT.EDU>, Brad Thompson <yak@MIT.EDU>,
aui@MIT.EDU
From: tb@MIT.EDU (Thomas Bushnell, BSG)
Date: 06 Jun 2000 13:25:32 -0400
In-Reply-To: Richard Tibbetts's message of "Mon, 05 Jun 2000 23:07:35 -0400"
Message-ID: <u1h4s76vi0j.fsf@pusey.mit.edu>
Richard Tibbetts <tibbetts@MIT.EDU> writes:
> My personal feelings here would be to modify the code and try to make
> the changes such that they would be accepted upstream (for instance, I
> would hope to be able to do this for any AFS stuff).
Certainly this is the first priority. (Incidentally, as for AFS,
don't assume that the existence of /afs means that the system is
running AFS and don't use avoid-AFS-lossage behavior on non-AFS files
[shell utils got both of these wrong]).
> In instances where the functionality is unlikely to be desirable
> upstream, or would be much harder to implement in an upstream friendly
> way (ie, gsm hacks to support moving between different platforms
> though the use of ATHENA_SYS) then we just lose.
I think in that case, the solution is generally to have Athena add a
new configuration option, and we turn it on in the user's files. (As
a general strategy; there are hard cases that don't fit that model
well.)
