9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] p9p mk issue
Date: Thu, 22 Nov 2007 10:47:33 -0500	[thread overview]
Message-ID: <20071122154724.7D3D01E8C22@holo.morphisms.net> (raw)
In-Reply-To: <20071121180107.531D55B2E@mail.bitblocks.com>

> 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


  parent reply	other threads:[~2007-11-22 15:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20 21:01 Bakul Shah
2007-11-20 21:08 ` Pietro Gagliardi
2007-11-20 21:44 ` Pietro Gagliardi
2007-11-20 22:20   ` Jeff Sickel
2007-11-20 22:48     ` Bakul Shah
2007-11-21  7:44       ` John Stalker
2007-11-21 16:01       ` Russ Cox
2007-11-21 18:01         ` Bakul Shah
2007-11-21 19:57           ` Pietro Gagliardi
2007-11-22 15:47           ` Russ Cox [this message]
2007-11-22 17:43             ` Bakul Shah
2007-11-22 18:20               ` Martin Neubauer
2007-11-22 19:48               ` Russ Cox
2007-11-30 18:01                 ` Bakul Shah
2007-11-30 19:01                   ` Russ Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071122154724.7D3D01E8C22@holo.morphisms.net \
    --to=rsc@swtch.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).