[5627] in Release_7.7_team

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

Potentially removing olc from the release?

daemon@ATHENA.MIT.EDU (Jonathan D Reed)
Mon Oct 16 16:51:18 2006

Date: Mon, 16 Oct 2006 16:51:08 -0400 (EDT)
From: Jonathan D Reed <jdreed@MIT.EDU>
To: release-team@MIT.EDU
Message-ID: <Pine.LNX.4.62L.0610161638001.30738@infinite-loop.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 1.218
X-Spam-Level: * (1.218)
X-Spam-Flag: NO


Hello,

At owls today, we talked about OLC's desire to move to RT as a ticket 
tracking system.  This obviously has various implications, as olc is in 
the release.

What we came up with is the following proposal:

-olc, olcr, olist, oreplay, oshow, xbrowser, and xolc all become 
attachandrunscripts which run binaries of the same name out of the "olc" 
locker (which I just created and will populate shortly).  The various man 
pages and help files are also removed and will be put in the "olc" locker.

-olc_browser is changed to an attachandrun script that has the same 
content as /usr/athena/bin/olc_answers

-olcd, olcm, polld, and rpd are completely removed from the release and 
not replaced by anything.  Jonathon Weiss notes that Ops has no objections 
to this.

I think that's everything that's in the release, going by the athena-olc 
package.

After those changes have been made, we will change the software in the 
locker once we actually make the transition to RT.  The new 'olc' will be 
a limited functionality perl script which informs people about the change 
and has "ask" and "answers" features that behave somewhat like they do 
now.

It was noted that there are plenty of machines still running older 
releases which will not get this update and thus still have the old olc 
client, and we are investigating workaround for that situation. 
Basically, we'll keep matisse around for a while, but attempt to inform 
users that it will go away eventually.

Additionally, there is the point that the default dotfiles run "olc who". 
Our "new" olc client will have a stub 'who' command which simply reports 
"You are not connected to a user." so that the dotfiles will still work. 
Eventually, that command can be removed from the dotfiles, but there will 
of course still be users who edited their own .cshrc and .bashrc files.

I think that covers any potential problems from this transition.  Does 
this proposal sound ok?  What would be the timeframe for turning the olc 
client programs into attachandrun scripts?  I can have the olc locker 
populated shortly.

Thanks,

Jon

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