[75] in Release_7.7_team

home help back first fref pref prev next nref lref last post

another last minute item

daemon@ATHENA.MIT.EDU (Dorothy Bowe)
Tue Apr 26 14:00:08 1994

To: release-77@MIT.EDU
In-Reply-To: 
Date: Tue, 26 Apr 94 13:57:15 EDT
From: Dorothy Bowe <dot@MIT.EDU>


As many of you probably read this morning, TPS is looking into
overhauling the IS/CSS/TPS documentation set and eventually replacing
the current versions of olh with WWW clients.  In order to prepare for
this, they'd like to replace the olh_motif and olh_ascii clients
currently on the packs with versions in a locker.  This will make it
easier to make changes to them later.

I have several questions for us as the release team.  One is something
of a formality, but do we all agree that this is okay to do?  Yes, it is
another attach-and-run script, but there is a good reason, I think.  

A second question, and this probably directed at Mark, is, can we get it
done?  I asked Chris Vanharen if there would be any complications in
moving the binaries but he has no.  I can set up a locker with the three
platforms' binaries but someone needs to make a couple of changes to
/usr/athena/bin/olh:

pianoforte[~][83] diff /tmp/olh /usr/athena/bin/olh
48,50c48
< /bin/athena/attach olh
< mach=`/bin/athena/machtype`
< olh_program=/mit/olh/${mach}bin/olh_${style}
---
> olh_program=/usr/athena/bin/olh_${style}

My third and final question is, assuming that we all think it's okay to
do *and* it is possible to get done, can anyone think of a reason why we
shouldn't do it?  My only fear is rushing to do something and
overlooking a complication.  But then, almost everything will be in a
locker and thus be more easily "fixed".

Thanks for your time,

	./dot

home help back first fref pref prev next nref lref last post