Rationalise ./configure
- borrow a lot of ideas from Michael ABBOTT ( http://sourceware.org/ml/crossgcc/2008-12/msg00030.html )
- should be conforming to POSIX 1003.1-2008, non compliance due to bashsims is to be considered a bug
- as a result, it now works with dash
- make a little easier to read in some places
- enforce 4-space indentation
- get rid of futile 'return $?'
- quote all variables assignments
- save and restore IFS prior to and after using alternate values
- simplify the TOOLS_TO_CHECK listing

What's left:
- provide a mean to actually _compare_ version numbers
- change the TOOLS_TO_CHECK pattern style to be able to use '|' in regexp

/trunk/configure | 243 127 116 0 ++++++++++++++++++++++++++++++++------------------------------
1 file changed, 127 insertions(+), 116 deletions(-)

#!/bin/sh

# Yes, this intends to be a true POSIX script file.

myname="$0"

doUsage() {

  cat <<_EOF_

Usage: ${myname} <dir> <base> <inc>

    Will renumber all patches found in <dir>, starting at <base>, and with

    an increment of <inc>

    Eg.: patch-renumber patches/gcc/4.3.1 100 10

_EOF_

}

[ $# -eq 3 ] || { doUsage; exit 1; }

[ -d "${1}" ] || { doUsage; exit 1; }

dir="${1}"

cpt="${2}"

inc="${3}"

case $(LC_ALL=C svnversion 2>/dev/null) in

    exported)   CMD="mv -v";;

    *)          CMD="svn mv";;

esac

for p in "${dir}"/*.patch; do

    [ -e "${p}" ] || { echo "No such file '${p}'"; exit 1; }

    newname="$(printf "%03d" ${cpt})-$(basename "${p}" |sed -r -e 's/^[[:digit:]]{3}-//')"

    [ "${p}" = "${dir}/${newname}" ] || ${CMD} "${p}" "${dir}/${newname}"

    cpt=$((cpt+inc))

done