DASH Shell discussions
 help / color / mirror / Atom feed
From: Antti Kantee <pooka@rumpkernel.org>
To: dash@vger.kernel.org, rumpkernel-users@freelists.org
Subject: Re: Dash commit 46d3c1a (in 0.5.8+) breaks BSD make
Date: Fri, 4 Mar 2016 14:24:17 +0000	[thread overview]
Message-ID: <56D99A91.2010901@rumpkernel.org> (raw)
In-Reply-To: <20160304140635.GB2457@nodbug.lucina.net>

On 04/03/16 14:06, Martin Lucina wrote:
> Commit 46d3c1a ([VAR] Sanitise environment variable names on entry)
> restricts exported environment variables actually set by dash on entry to
> those reported as valid by endofname(). While this is technically correct
> and matches IEEE Std 1003.1, it breaks BSD make which uses '.' as a
> separator in variables exported via the environment to a sub-make.

I wouldn't go so far as to say it breaks BSD make.  Rather, it breaks a 
rare pattern where variables containing "." (where "." follows a certain 
convention) are passed to submakes via the shell (i.e. ".export" in the 
Makefile).

> Would the dash maintainers consider replacing 46d3c1a with a fix that
> performs the name validity check at "export -p" time instead? If yes, I can
> try my hand at a patch.

There are probably enough deployments of dash with this behaviour so 
that we need in any case need to remove the use of variables containing 
"." coupled with ".export" from Makefiles.  Changing dash doesn't sound 
useful to me.

  reply	other threads:[~2016-03-04 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04 14:06 Dash commit 46d3c1a (in 0.5.8+) breaks BSD make Martin Lucina
2016-03-04 14:24 ` Antti Kantee [this message]
2016-03-04 15:48   ` Martin Lucina

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=56D99A91.2010901@rumpkernel.org \
    --to=pooka@rumpkernel.org \
    --cc=dash@vger.kernel.org \
    --cc=rumpkernel-users@freelists.org \
    /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