From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] p9p mk issue 
From: "Russ Cox" <rsc@swtch.com>
Date: Thu, 22 Nov 2007 10:47:33 -0500
In-Reply-To: <20071121180107.531D55B2E@mail.bitblocks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20071122154724.7D3D01E8C22@holo.morphisms.net>
Topicbox-Message-UUID: 085aa562-ead3-11e9-9d60-3106f5b1d025

> OK, how about this?  If env. var MKSHELL is set to rc, then
> set the default value of make variable MKSHELL to rc else to
> sh.  You get exactly the same effect as now and I get what I
> want by setting MKSHELL env. var to rc.

No.  The fact is that some mkfiles are written with rc
recipes and some with sh recipes.  Setting a global default
is going to break one or the other.  It is just not that hard
to write 

MKSHELL=rc

if you start using complicated rc constructs.  The vast
majority of recipes one writes in mkfiles tend to be 
valid sh and rc syntax anyway, so I would not expect
that you'd have to put that in many mkfiles.

Also, if you have lots of complicated scripts in all your
mkfiles, maybe you are missing a chance to refactor 
the complication into a single included mkfile that 
can have MKSHELL=rc in it.  Then you've only got one.

Russ