tools/testrel

#!/bin/sh

# release test
PYVER=`python -V 2>&1 | awk '{print $2}' | awk -F '.' '{print $1$2}' `

# clean up build/dist directories
rm -rf ~/ipython/ipython/build/*
rm -rf ~/ipython/ipython/dist/*

# build source distros
cd ~/ipython/ipython

./setup.py sdist --formats=gztar

#./setup.py bdist_rpm --release=py$PYVER
python2.3 ./setup.py bdist_rpm --release=py23 --python=/usr/bin/python2.3
python2.4 ./setup.py bdist_rpm --release=py24 --python=/usr/bin/python2.4

# Call the windows build separately, so that the extra Windows scripts don't
# get pulled into Unix builds (setup.py has code which checks for
# bdist_wininst)
#./setup.py bdist_wininst --install-script=ipython_win_post_install.py

# For now, make the win32 installer with a hand-built 2.3.5 python, which is
# the only one that fixes a crash in the post-install phase.
$HOME/tmp/local/bin/python2.3 setup.py bdist_wininst \
  --install-script=ipython_win_post_install.py