From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andreas Mohr <andi@lisas.de>
Cc: 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: Wed, 31 Oct 2007 15:24:22 -0700 [thread overview]
Message-ID: <47290096.7080207@oracle.com> (raw)
In-Reply-To: <20071031211321.GA8363@rhlx01.hs-esslingen.de>
Andreas Mohr wrote:
> Hello,
>
> I was non-mildly horrified to find that the rather widely used patch-kernel
> script seems to rely on bash despite specifying the interpreter as #!/bin/sh,
> since my dash-using Debian install choked on it.
>
> Thus I'm delivering a first, preliminary, non-reviewed change to make
> patch-kernel (a little bit more?) POSIX-compatible. It now survives both
> a dash and a bash run.
>
> If this mail goes through relatively unscathed, then it might be a good
> idea to plant it into -mm via a follow-up mail.
>
> Comments?
>
> - replaced "==" by "="
Those are OK.
> - the "source" statement most likely needs the ./ prepended, as can be
> gathered from e.g. http://osdir.com/ml/colinux.devel/2005-12/msg00036.html
That email isn't very convincing to me.
http://www.opengroup.org/onlinepubs/009695399/utilities/dot.html just says that
if <filename> does not contain a slash, the search PATH shall be used (searched).
If you want to prevent that, it's OK to use ./, but at least say that in the
patch description, please.
> - the newly replaced sed expression below: is it ok? correct? strict enough?
>
> Thanks,
>
> Andreas Mohr
>
> (who's strongly hoping that submitting a patch for this thingy doesn't
> automatically equal becoming "maintainer for life" for it ;)
Be careful.
> --- linux-2.6.23/scripts/patch-kernel 2007-10-31 21:55:26.000000000 +0100
> +++ linux-2.6.23/scripts/patch-kernel.dash 2007-10-31 21:58:37.000000000 +0100
> @@ -202,13 +202,7 @@
> EXTRAVER=
> if [ x$EXTRAVERSION != "x" ]
> then
> - if [ ${EXTRAVERSION:0:1} == "." ]; then
> - EXTRAVER=${EXTRAVERSION:1}
> - else
> - EXTRAVER=$EXTRAVERSION
> - fi
> - EXTRAVER=${EXTRAVER%%[[:punct:]]*}
> - #echo "$PNAME: changing EXTRAVERSION from $EXTRAVERSION to $EXTRAVER"
What's the problem above?
> + EXTRAVER=`echo $EXTRAVERSION|sed -s 's/^[\.]\?\([^[:punct:]]*\).*/\1/'`
> fi
>
> #echo "stopvers=$stopvers"
> @@ -251,16 +245,16 @@
> do
> CURRENTFULLVERSION="$VERSION.$PATCHLEVEL.$SUBLEVEL"
> EXTRAVER=
>
> - SUBLEVEL=$((SUBLEVEL + 1))
> + SUBLEVEL=$(( $SUBLEVEL + 1 ))
Why are the added spaces needed?
Did you look at
http://www.opengroup.org/onlinepubs/000095399/utilities/xcu_chap02.html ?
> FULLVERSION="$VERSION.$PATCHLEVEL.$SUBLEVEL"
> #echo "#___ trying $FULLVERSION ___"
>
> - if [ $((SUBLEVEL)) -gt $((STOPSUBLEVEL)) ]; then
> + if [ $SUBLEVEL -gt $STOPSUBLEVEL ]; then
What's the problem here?
> echo "Stopping since sublevel ($SUBLEVEL) is beyond stop-sublevel ($STOPSUBLEVEL)"
> exit 1
> fi
--
~Randy
next prev parent reply other threads:[~2007-10-31 22:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 21:13 [PATCH/RFC] eradicate bashisms in scripts/patch-kernel Andreas Mohr
2007-10-31 22:24 ` Randy Dunlap [this message]
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
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=47290096.7080207@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@osdl.org \
--cc=andi@lisas.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.