Package Details: doomrl 0.9.9.7-11

Git Clone URL: https://aur.archlinux.org/doomrl.git (read-only, click to copy)
Package Base: doomrl
Description: A roguelike game based on the FPS Doom.
Upstream URL: http://drl.chaosforge.org/
Keywords: game roguelike
Licenses: GPL, CCPL:cc-by-nc-sa-4.0
Submitter: None
Maintainer: gileri
Last Packager: gileri
Votes: 63
Popularity: 0.001476
First Submitted: 2007-02-12 10:19 (UTC)
Last Updated: 2023-11-26 16:45 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

CyberShadow commented on 2016-08-23 15:10 (UTC)

Seriously? suid as root? There is no reason why a *video game* should run as root! You could either: - suid as a new doomrl user - make the global directory writable by all (e.g. owned by "games" group, set sticky on directories) - write a wrapper to copy/link game files to a directory under the user's home directory (e.g. ~/.local/share/doomrl/) - patch or badger upstream to respect XDG directory conventions

bsdbeard commented on 2015-03-20 14:56 (UTC)

This PKGBUILD isn't right, it doesn't contain the package() function at all and mkdir -p "$pkgdir/usr/share/doomrl" will complain it can't create directories, here's a fixed PKGBUILD that works: # Contributor: KillaB <xGenoBlast@gmail.com> # Contributor: wizzomafizzo <wizzomafizzo@gmail.com> # Contributor: Nick <nick@screamingfist.org> # Maintainer: Jupotter <jupotter.g@gmail.com> pkgname=doomrl pkgver=0.9.9.7 pkgrel=1 pkgdesc="A roguelike game based on the FPS Doom." arch=('i686' 'x86_64') url="http://doom.chaosforge.org/" license=("custom") depends=("sdl_mixer" "zlib" "lua" "timidity-eawpatches" "sdl_image") conflicts=("doomrl-lq doomrl-ogg") source=("http://doom.chaosforge.org/file_download/33/doomrl-linux-i386-0997.tar.gz" "doomrl" "LICENSE") md5sums=('f1beebc47c63a768752ea66951799f45' '825cac701303cd5c61ec209e461219de' 'eaa0c779f98be421bf34cd0c5800642a') [ "$CARCH" == "x86_64" ] && source=("http://doom.chaosforge.org/file_download/32/doomrl-linux-x64-0997.tar.gz" "doomrl" "LICENSE") [ "$CARCH" == "x86_64" ] && md5sums=('7078b52000b91c468a0041ff667c4f81' '825cac701303cd5c61ec209e461219de' 'eaa0c779f98be421bf34cd0c5800642a') package() { if [ "$CARCH" == "x86_64" ] ; then cd "$srcdir/doomrl-linux-x64-${pkgver//./}" else cd "$srcdir/doomrl-linux-i386-${pkgver//./}" fi # Copy program and required files install -d "$pkgdir/usr/share/doomrl" cp -a * "$pkgdir/usr/share/doomrl" # Copy script used to run program install -D -m755 "$srcdir/doomrl" "$pkgdir/usr/bin/doomrl" # Copy the license file install -D -m644 "$srcdir/LICENSE" \ "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE" # This is needed to save games and scores chmod 4755 "$pkgdir/usr/share/doomrl/doomrl" }

r0b0h0b0 commented on 2015-02-24 06:55 (UTC)

:: Checking doomrl integrity... ==> ERROR: Missing package() function in /doomrl/build/folder/ :: failed to verify doomrl integrity

ecastilla commented on 2013-12-28 05:18 (UTC)

I am getting the same problem as stecco. I've tried various attempts at debugging with gdb and setting processor affinity to one core. Game plays fine if you disable all music from the config. Activiting the EAW config did not help. Probably related to how the game plays mp3s as Awebb suggests.

stecco commented on 2013-11-15 09:59 (UTC)

doomrl-lq seems to work fine. could the problem be timidity-eawpatches? It's orphan...

Jupotter commented on 2013-11-15 09:43 (UTC)

The libpng warning comes from the latest version of libpng, it should not affect the program. Did you try using the ogg or lq version for the crash?

stecco commented on 2013-11-15 09:34 (UTC)

I downloaded and compiled successfully the package, but when I try to run from my terminal, after the second screen doomrl crashes and I have this: http://pastebin.com/3VykWjgj Any ideas?

idonthack commented on 2013-03-20 11:57 (UTC)

version 0.9.9.7 is out made a pkgbuild http://ix.io/4Ou

Awebb commented on 2013-01-26 14:19 (UTC)

The arch-specific stuff is indeed messed up, as the package is called …i386…, but the arch is …i686…. One can solve this manually in the PKGBUILD, but we should come up with something more permanent. Another sidenote: It is crucial to activate the EAW config in timidity-eawpatches, as the install note tells you to. You might and will run into segfaults otherwise (when saving stats or entering "The Wall"). I have not had a single segfault, since I did this.

« First ‹ Previous 1 2 3 4 5 Next › Last »