From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Add test infrastructure
Date: Sun, 4 Mar 2012 14:01:40 +0100 [thread overview]
Message-ID: <201203041401.40738.arnout@mind.be> (raw)
In-Reply-To: <201203040113.27598.yann.morin.1998@free.fr>
On Sunday 04 March 2012 01:13:27 Yann E. MORIN wrote:
[snip]
> > +testdir=$(dirname $0)
> > +topdir=$(cd $testdir/..; pwd)
>
> I would highly suggest using ${foo} instead of $foo because it makes
> it explicit what the variable name is. Also, enclose variable between
> double-quotes, in case a vicious user uses a dir with a space in it.
Spaces will make 'make' barf, so aren't supported anyway. But * and
other ugly stuff would indeed be possible, so I've added quotes
everywhere.
[snip]
> See the "The Open Group Base Specifications Issue 7", utilities chapter 2,
> dealing about "Shell Command Language":
> http://pubs.opengroup.org/onlinepubs/9699919799/toc.htm
> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html
That's a useful reference! I'll look at that more often, thanks!
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-03-04 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 23:45 [Buildroot] Test infrastructure Arnout Vandecappelle
2012-03-03 23:45 ` [Buildroot] [PATCH 1/2] Add target to print buildroot version Arnout Vandecappelle
2012-03-03 23:45 ` [Buildroot] [PATCH 2/2] Add test infrastructure Arnout Vandecappelle
2012-03-04 0:13 ` Yann E. MORIN
2012-03-04 13:01 ` Arnout Vandecappelle [this message]
2012-03-05 14:56 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-06 7:06 ` Arnout Vandecappelle
2012-03-06 8:29 ` Thomas Petazzoni
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=201203041401.40738.arnout@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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