From: Andreas Mohr <andi@lisas.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Randy Dunlap <rdunlap@xenotime.net>, Andreas Mohr <andi@lisas.de>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/RFC] eradicate bashisms in scripts/patch-kernel
Date: Fri, 2 Nov 2007 21:09:35 +0100 [thread overview]
Message-ID: <20071102200935.GA14153@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <20071102020118.GA13852@gondor.apana.org.au>
Hi,
On Fri, Nov 02, 2007 at 10:01:18AM +0800, Herbert Xu wrote:
> On Thu, Nov 01, 2007 at 04:08:57PM -0700, Randy Dunlap wrote:
> > I think that this is the part that bothers me. I can't find
> > anything at
> > http://www.opengroup.org/onlinepubs/000095399/utilities/xcu_chap02.html
> > that says that this:
> > EXTRAVER=${EXTRAVER%%[[:punct:]]*}
> >
> > is invalid or even optional syntax. OTOH, it does list such syntax,
>
> This is POSIX-compliant and has worked with dash from the very
> start.
True (just verified again). But then I didn't actually say that this line
is problematic. Since I had to replace the leading . replacement part already
I decided to simply fold everything into one sed expression.
> Using variables without dollar signs in arithmetic expansion was
> only added to dash very recently. So please please talk to your
> distribution maker to update their dash packages and it will work
> correctly.
"Debian stable.", aka "Update not an option.". Right?
Since the specs list both possibilities I'd simply go with the safe one,
the one that works on older dash versions, too.
Unless adding a $ sign happens to break other equally important
shells...
> This usage is compliant with the most recent revision of POSIX
> while earlier ones did not specifically require this (due to
> the fact that assignment support was not required either).
This is where I'd think the problem is. If dash once upon a time
decided to support the $ variant only and the specs didn't list both
at that time, well...
The dash version on my system is 0.5.3-5, BTW. Even Debian testing
has 0.5.3-7 only.
I'm now quite certain on which side to tweak things ;)
Thanks a lot for your review,
Andreas Mohr
next prev parent reply other threads:[~2007-11-02 20:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 21:13 Andreas Mohr
2007-10-31 22:24 ` Randy Dunlap
2007-11-01 12:11 ` Andreas Mohr
2007-11-01 15:24 ` Randy Dunlap
2007-11-01 22:16 ` Andreas Mohr
2007-11-01 23:08 ` Randy Dunlap
2007-11-02 2:01 ` Herbert Xu
2007-11-02 20:09 ` Andreas Mohr [this message]
2007-11-02 20:17 ` Randy Dunlap
2007-11-05 19:58 ` Andreas Mohr
2007-11-14 22:46 ` Randy Dunlap
2007-11-17 16:33 ` Andreas Mohr
2007-11-17 16:43 ` Herbert Xu
2007-11-17 17:28 ` Sam Ravnborg
2007-11-17 20:51 ` [PATCH] " Andreas Mohr
2008-01-02 23:00 ` Randy Dunlap
2011-04-03 18:58 ` [PATCH] " Andreas Mohr
2011-04-03 19:40 ` Randy Dunlap
2011-04-21 11:36 ` Andreas Mohr
2011-04-04 12:59 ` Michal Marek
2007-11-17 17:24 ` [PATCH/RFC] " Adrian Bunk
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=20071102200935.GA14153@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--cc=akpm@osdl.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.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
all inboxes | Powered by JetHome®