They are preparing a new release of Death Rally http://www.eurogamer.net/articles/2012-06-29-death-rally-announced-for-pc so maybe that's why they did some cleaning up.
Search Criteria
Package Details: death-rally 1.0-4
Package Actions
- View PKGBUILD
- Download tarball
- Search wiki
- Flagged out-of-date (2013-06-10)
| Package Base: | death-rally |
|---|---|
| Description: | A free windows port of the classic racing game from Remedy games, played in Wine. |
| Upstream URL: | http://www.abandonia.com/en/games/28518/Death+Rally.html |
| Category: | games |
| Licenses: | |
| Submitter: | WFCody |
| Maintainer: | None |
| Last Packager: | None |
| Votes: | 7 |
| First Submitted: | 2011-02-26 11:16 |
| Last Updated: | 2011-06-15 08:01 |
Dependencies (2)
Required by (0)
Sources
Latest Comments
Comment by karol_007
Anonymous comment
Hello, for some reason it has been taken away from the Remedy website.
http://gamedaily.newaol.com/pub/DeathRallyWin_10.exe?ru=19&h=00db2285da8ff31c25a7628be58182a5
here is a new source, just change the package to this source and add
mv $srcdir/DeathRallyWin_10.exe?ru=19&h=00db2285da8ff31c25a7628be58182a5 $srcdir/DeathRallyWin_10.exe
to build().
Comment by silent
I tried to install the death-rally AUR package with yaourt as root on a x86-64 system. The biggest problem was that some lib32 video drivers were missing and so launching Death Rally has frozen the Xorg and I had to kill it manually. The other problem was that after the uninstall ~/.local/share/applications/wine folder has not been removed and was owned by root, so menu generation for other wine installs did not work, besides the entries in it pointed to a wine install in /tmp. After installing the lib32 packages I downloaded the .exe from the above link and installed it simply with wine. Now it works well. So it is better to use simply makepkg instead of yaourt, and make sure that lib32 staff is installed for wine on x86-64 systems.
Comment by karol_007
It works fine, thanks a lot :-)
Comment by WFCody
ok :) I will make a quick update then :)
Comment by karol_007
> If you want I can disown the package for now to let you play with it.
Nah, it's fine, you can keep it :-)
The assignement somehow doesn't work here. I've created two little scripts, called test1 and test2; they differ only by the two spaces around that dreadfull '=':
[karol@white death-rally]$ echo $CARCH
i686
[karol@white death-rally]$ diff test1 test2
3c3
< if [ ${CARCH}=x86_64 ]
---
> if [ ${CARCH} = x86_64 ]
[karol@white death-rally]$ cat test1
#!/bin/bash
if [ ${CARCH}=x86_64 ]
then
echo "drive_c/Program\ (\x86\)/Death\ Rally/"
else
echo "drive_c/Program\ Files/Death\ Rally/"
fi
[karol@white death-rally]$ ./test1
drive_c/Program\ (\x86\)/Death\ Rally/
[karol@white death-rally]$ cat test2
#!/bin/bash
if [ ${CARCH} = x86_64 ]
then
echo "drive_c/Program\ (\x86\)/Death\ Rally/"
else
echo "drive_c/Program\ Files/Death\ Rally/"
fi
[karol@white death-rally]$ ./test2
drive_c/Program\ Files/Death\ Rally/
test2 works for me, test1 doesn't. But it's no big deal, I can handle it ;P
Comment by WFCody
hmm weird. If you want I can disown the package for now to let you play with it. The strange thing is that it works over here...
Comment by karol_007
I'm on i686 and I still get the same error as before: /usr/bin/deathrally: 5: Syntax error: "(" unexpected
Instead of 'if [ ${CARCH}=x86_64 ]' it should say 'if [ ${CARCH} = x86_64 ]' (added spaces before and after '=').
Comment by WFCody
Updated to deal with differences between wine32 and wine64
Comment by WFCody
Ah... I think I know why. If you run Wine64 it makes two different Program directories.
I will make the $_winedir variable conditional based on architecture.
Comment by karol_007
I'm having problems with this line:
_winedir="drive_c/Program\ (\x86\)/Death\ Rally/"
'Program\ (\x86\)'? Correcting it to 'Program\ Files' works :-)
Comment by WFCody
updated to unclutter ~/ with a common .abandonia directory. A common standard for several abandonia packagers...
Comment by karol_007
@WFCody
I'm terribly sorry, your PKGBUILD clearly says why do you need unionfs. I've been playing this game in wine for a long time w/o unionfs so I was surprised to see an additional dependency.
Comment by WFCody
unionfs used for per-user settings etc. I hope you enjoy this one as much as I do. Runs nicely :)