Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cuae2!ihnp4!ptsfa!lll-lcc!ames!oliveb!sun!gorodish!guy
From: guy@gorodish.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: \"special\" shells a security hole?
Message-ID: <13252@sun.uucp>
Date: Fri, 13-Feb-87 00:31:42 EST
Article-I.D.: sun.13252
Posted: Fri Feb 13 00:31:42 1987
Date-Received: Sat, 14-Feb-87 13:55:16 EST
References: <3953@brl-adm.ARPA> <2590002@hpisod2.HP>
Sender: news@sun.uucp
Reply-To: guy@sun.UUCP (Guy Harris)
Organization: Sun Microsystems, Mountain View
Lines: 14

>If I want to use Korn shell constructs in my Makefile, then
>there ought to be a general, clean way of doing it, such as
>"SHELL=/bin/ksh".

That ain't general - the Korn shell is in "/usr/local/ksh" on my
machine, and there may not *be* a Korn shell on other machines (which
means there *is* no general way to use Korn shell constructs in your
Makefile - period).

Furthermore, it is a botch to *import* SHELL from the environment;
this causes Makefiles to work differently for people with different
login shells!  "make" should NOT import SHELL; if people insist on
being able to use other shells, perhaps it should allow you to change
SHELL from within the Makefile and ONLY from within the Makefile.