Nexuiz-2.5-2 to nexuiz-2.5.1 package patch

Question

This only concerns users who currently have nexuiz-2.5-2 installed.
If you want to upgrade to 2.5.1 without downloading the full 600+ MB package, use the following PKGBUILD which uses the patch provided by Alientrap.
# Contributor: Xyne
# Contributor: Jaroslaw Swierczynski <[email protected]>
# Contributor: Roman Kyrylych <[email protected]>
# Contributor: Camille Moncelier <[email protected]>
pkgname=nexuiz
pkgver=2.5.1
_zipver=$(echo $pkgver | sed 's/\.//g')
pkgrel=1
arch=('i686' 'x86_64')
pkgdesc="a free, open-source first person shooter"
url="http://www.nexuiz.com/"
license=("GPL")
depends=('alsa-lib' 'curl' 'libjpeg' 'libmodplug' 'libvorbis' 'libxpm' 'libxxf86dga' 'libxxf86vm' 'sdl')
makedepends=('mesa')
source=(http://downloads.sourceforge.net/$pkgname/${pkgname}patch-$_zipver.zip)
md5sums=('8c3625a1ed2b1f26a1f9943eeb19be0f')
build() {
if [ ! -f "/var/lib/pacman/local/nexuiz-2.5-2/files" ]; then
echo "the package nexuiz-2.5-2 was not found on your system"
echo "this PKGBUILD will only patch nexuiz-2.5-2"
return 1
fi
for _FILE in $(cat /var/lib/pacman/local/nexuiz-2.5-2/files); do
[ "$_FILE" == '%FILES%' ] && continue
_OLD_PATH="/$_FILE"
[ -f "$_OLD_PATH" ] || continue
echo "copying $_OLD_PATH"
_NEW_PATH="$pkgdir/$_FILE"
_NEW_DIR=$(dirname $_NEW_PATH)
mkdir -p "$_NEW_DIR"
cp "$_OLD_PATH" "$_NEW_PATH"
done
_nexdir="$pkgdir/opt/nexuiz"
_enginesource_date="20090501"
_install_dir $srcdir/Nexuiz/Docs $_nexdir/docs
_install_dir $srcdir/Nexuiz/data $_nexdir/data
_install_dir $srcdir/Nexuiz/havoc $_nexdir/havoc
_install_dir $srcdir/Nexuiz/server $_nexdir/server
find $_nexdir/server -name "*_windows.bat" -exec rm {} \;
find $_nexdir/server -name "*_mac.sh" -exec rm {} \;
cd $srcdir/Nexuiz
bsdtar -x -f sources/enginesource${_enginesource_date}.zip || return 1
cd darkplaces
# here's a working kludge to build all three binaries at once but don't use it ;)
# make CPUOPTIMIZATIONS="${CFLAGS}" nexuiz || make CPUOPTIMIZATIONS="${CFLAGS}" nexuiz || return 1
# build the binaries separately instead to avoid truncated files
make CPUOPTIMIZATIONS="${CFLAGS}" cl-nexuiz || return 1
make CPUOPTIMIZATIONS="${CFLAGS}" sdl-nexuiz || return 1
make CPUOPTIMIZATIONS="${CFLAGS}" sv-nexuiz || return 1
# install the compiled binaries
install -Dm755 nexuiz-glx nexuiz-sdl nexuiz-dedicated -t $_nexdir
function _install_dir {
_src_dir=$1
_dest_dir=$2
_n=${#_src_dir}
for _file in $(find $_src_dir -type f)
do
_dest_file=${_dest_dir}${_file:$_n}
install -Dm644 $_file $_dest_file
done
If you do not yet have Nexuiz installed, wait until I upload the latest version (nexuiz-2.5.1).

Answer 1

Hello Tarek,
There are 2 possible ways of migrating a TopLink 2.5 builder based project and it's associated "text" files (i.e. .descriptor, .topclass, .etc) to TopLink 9.0.3:
1a> Run the 9.0.3 package renamer on the Java files (and recompile). Then...
1b> Manually create the 9.0.3 mapping workbench .mwp project and create the "newer" XML versions of the descriptor, class and table files by using the "old" 2.5 based files as a guide.
OR...
2a> Convert the 2.5 project first to an older version of TopLink (i.e 4.0.2)
2b> Use the 4.0.2 project renamer and then import the 2.5 .project file into the 4.0.2 mapping workbench.
2c> After this process is done, repeat again to convert the 4.0.2 project to version 9.0.3.
Hope this helps.
Martin
Strategic Implementation Consultant
Oracle9iAS Technical Services