1 Missing dependency The readme-postinstall asks the user to copy files into /usr/share/games/quake2-data/baseq2/: To install the Quake2 gamedata from game CD: -------------------------------------------- (assuming the cdrom is mounted at /cdrom) 1. cp /cdrom/Install/Data/baseq2/pak0.pak /usr/share/games/quake2-data/baseq2/ 2. cp /cdrom/Install/Data/baseq2/video/ /usr/share/games/quake2-data/baseq2/ (optional) However this directory isn't available until one emerges the quake2-data ebuild. I think it would be good to make the quake2-data ebuild a dependency of icculus. 2 Sound issues I only could get icculus working without the alsa useflag. maybe we should remove this useflag? Furthermore I noticed sound only works if the 'sound quality' is set to 'high'. Reproducible: Always Steps to Reproduce: See Description
Change summary to mention the ebuild you're referring to: quake2-icculus See /usr/portage/games-fps/quake2-icculus/quake2-icculus-0.16.1-r1.ebuild: RDEPEND="${UIDEPEND} cdinstall? ( games-fps/quake2-data ) demo? ( games-fps/quake2-demodata )" ... if ! use sdl ; then ewarn "The ALSA sound driver for this game is broken." ewarn "The 'sdl' USE flag is recommended instead." For a decent Quake 2 client, take your pick from http://forums.gentoo.org/viewtopic-p-3777588.html#3777588 The best thing to do with the quake2-icculus ebuild is to *remove* it, as it seems to be dead upstream, and has current & better replacements provided by QuDos.
The sound doesn't work right for me with USE="-alsa sdl" either.
(In reply to comment #0) > However this directory isn't available until one emerges the quake2-data > ebuild. I think it would be good to make the quake2-data ebuild a dependency of > icculus. Uhh... except you don't *have* to merge quake2-data for this to work. All you need to do is create the directory and copy the files. Anyway, we've been pretty much maintaining quake2-icculus as UPSTREAM. Any patches we've been adding, I've been sending upstream, and they're willing to add patches, there just aren't any active developers on the project. In other words, upstream isn't doign any coding, but they aren't dead and the source isn't abandoned so long as they're still applying patches. I should probably get the other bug reports here all closed out and see if I can get upstream to roll up a new release with everything fixed in it.