[3111] in SIPB bug reports

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

"This program has been de-supported by the SIPB..."

daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Fri Aug 14 15:27:20 1992

Date: Fri, 14 Aug 92 15:26:25 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: chew@hplchew.hpl.hp.com
Cc: yandros@Athena.MIT.EDU, bug-sipb@Athena.MIT.EDU
In-Reply-To: chew@hplchew.hpl.hp.com's message of Fri, 14 Aug 92 11:39:01 PDT <9208141839.AA10540@hplchew.hpl.hp.com>

   Date: Fri, 14 Aug 92 11:39:01 PDT
   From: chew@hplchew.hpl.hp.com

   in the case of cal where a standard one exists that does the same thing,
   you should either punt it, or give the warning message then execute the
   standard path one.

I'd say that the script we install should only give a warning message
if either (a) it was invoked explicitly with /mit/sipb/bin/cal (or
whatever), rather than being searched for in the path (it should be
able to determine this by checking $0 or $argv[0] or whatever,
depending on what kind of script it is :-), or (b) it was invoked with
a two-digit year, since that's the only time our version functions
differently from the standard one.

It would not be difficult to write a script that is this smart.  And
it seems like the Right Thing in this case.

  jik

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