@@ -10,7 +10,7 @@ like '0.7.6' or 0.7.6-dev'.
1010Run from the top directory of the git checkout.
1111"
1212
13- FILES=" package/setup.py package/MDAnalysis/version.py testsuite/setup.py testsuite/MDAnalysisTests/__init__.py"
13+ FILES=" package/setup.py package/MDAnalysis/version.py testsuite/setup.py testsuite/MDAnalysisTests/__init__.py maintainer/conda/MDAnalysis/meta.yaml "
1414
1515die () {
1616 echo " ERROR: $1 "
@@ -19,40 +19,40 @@ die () {
1919
2020findcommand () {
2121 for name in $* ; do
22- path=$( which $name )
23- if [ -n " $path " ]; then
24- echo $path
25- return 0
26- fi
22+ path=$( which $name )
23+ if [ -n " $path " ]; then
24+ echo $path
25+ return 0
26+ fi
2727 done
2828 die " None of the commands $* found." 2
2929}
3030
3131sed_eregex () {
32- # does this sed understand extended regular expressions?
33- # - FreeBSD (Mac OS X) sed -E
34- # - GNU sed --regexp-extended (undocumented: also -E ...)
35- local SED=$1
36- if [ " good" = " $( echo ' bad' | $SED -E ' s/(abc)?bad|foo/good/' ) " ]; then
37- echo " $SED -E"
38- return 0
39- elif [ " good" = " $( echo ' bad' | $SED --regexp-extended ' s/(abc)?bad|foo/good/' ) " ]; then
40- echo " $SED --regexp-extended"
41- return 0
42- elif [ " good" = " $( echo ' bad' | $SED ' s/(abc)?bad|foo/good/' ) " ]; then
43- echo " $SED "
44- return 0
45- fi
46- echo " false"
47- return 1
32+ # does this sed understand extended regular expressions?
33+ # - FreeBSD (Mac OS X) sed -E
34+ # - GNU sed --regexp-extended (undocumented: also -E ...)
35+ local SED=$1
36+ if [ " good" = " $( echo ' bad' | $SED -E ' s/(abc)?bad|foo/good/' ) " ]; then
37+ echo " $SED -E"
38+ return 0
39+ elif [ " good" = " $( echo ' bad' | $SED --regexp-extended ' s/(abc)?bad|foo/good/' ) " ]; then
40+ echo " $SED --regexp-extended"
41+ return 0
42+ elif [ " good" = " $( echo ' bad' | $SED ' s/(abc)?bad|foo/good/' ) " ]; then
43+ echo " $SED "
44+ return 0
45+ fi
46+ echo " false"
47+ return 1
4848}
4949
5050while getopts h OPT; do
5151 case $OPT in
52- h) echo " $usage " ;
53- exit 0
54- ;;
55- \? ) exit 2;;
52+ h) echo " $usage " ;
53+ exit 0
54+ ;;
55+ \? ) exit 2;;
5656 esac
5757done
5858
@@ -62,11 +62,11 @@ RELEASE=$1
6262test -n " $RELEASE " || die " Required argument missing. See -h for help." 2
6363
6464# find a sed with -i and -E
65- for cmd in gsed sed; do
65+ for cmd in gsed sed; do
6666 SED=$( sed_eregex $( findcommand $cmd ) )
6767 [ " $SED " != " false" ] && break
6868done
69- [ " $SED " = " false" ] && { echo " ERROR: cannot find suitable sed." ; exit 1; }
69+ [ " $SED " = " false" ] && { echo " ERROR: cannot find suitable sed." ; exit 1; }
7070# should check for -i but we just hope for the best ...
7171# modern(ish) seds have -i
7272echo " Using sed = $SED "
@@ -75,7 +75,11 @@ echo "Setting RELEASE/__version__ in MDAnalysis to $RELEASE"
7575
7676git grep -E -l ' RELEASE.*[0-9]+\.[0-9]+\.[0-9]+(\.[0-9]+)?(dev|rc*[0-9])?' $FILES \
7777 | xargs -I FILE $SED ' /RELEASE/s/[0-9]+\.[0-9]+\.[0-9]+(\.[0-9]+)?(dev|rc*[0-9])?/' ${RELEASE} ' /' -i.bak FILE
78+
7879git grep -E -l ' __version__ =.*[0-9]+\.[0-9]+\.[0-9]+(\.[0-9]+)?(dev|rc*[0-9])?' $FILES \
7980 | xargs -I FILE $SED ' /__version__/s/[0-9]+\.[0-9]+\.[0-9]+(\.[0-9]+)?(dev|rc*[0-9])?/' ${RELEASE} ' /' -i.bak FILE
80- git status
8181
82+ git grep -E -l ' version:.*[0-9]+\.[0-9]+\.[0-9]+(\.[0-9]+)?(dev|rc*[0-9])?' $FILES \
83+ | xargs -I FILE $SED ' /version:/s/[0-9]+\.[0-9]+\.[0-9]+(\.[0-9]+)?(dev|rc*[0-9])?/' ${RELEASE} ' /' -i.bak FILE
84+
85+ git status
0 commit comments