GZDoom does this. I provide a patch in my GZDoom packages which should prevent GZDoom from replacing ZDoom's zdoom.ini, but if you have used unpatched GZDoom in past, you may already have your zdoom.ini overwritten by GZDoom.
Search Criteria
Package Details: zdoom-git 2.8pre.r1130.g72506fa-1
Package Actions
| Package Base: | zdoom-git |
|---|---|
| Description: | An enhanced Doom port with additional support for Heretic, Hexen and Strife (git version). |
| Upstream URL: | http://www.zdoom.org/ |
| Category: | games |
| Licenses: | |
| Conflicts: | |
| Provides: | |
| Submitter: | grubber |
| Maintainer: | grubber |
| Last Packager: | grubber |
| Votes: | 11 |
| First Submitted: | 2013-06-25 15:21 |
| Last Updated: | 2015-01-28 20:23 |
Dependencies (19)
- fluidsynth
- fmodex4.26.36
- gtk2
- gxmessage
- sdl2
- cmake (make)
- git (make)
- imagemagick (make)
- nasm (make)
- blasphemer (optional) – Blasphemer (free Heretic) game data
- chexquest3-wad (optional) – Chex Quest 3 game data
- doom1-wad (optional) – Doom shareware game data
- freedoom (optional) – FreeDoom game data
- hacx-wad (optional) – HacX game data
- harmony-wad (optional) – Harmony game data
- heretic1-wad (optional) – Heretic shareware game data
- hexen1-wad (optional) – Hexen demo game data
- strife0-wad (optional) – Strife shareware game data
- urbanbrawl-wad (optional) – Urban Brawl: Action Doom 2 game data
Required by (0)
Sources
- doom-share-dir.patch
- stack-noexec.patch
- zdoom.desktop
- zdoom
Latest Comments
Comment by grubber
Comment by Trist
The zdoom.ini found in ~/.config/zdoom was incorrect for me. This took me awhile to find out because I kept overlooking it I guess. All the results were marked for gzdoom directories. For example, /usr/share/games/gzdoom for zdoom.pk3, something that kept me frustrated for days. After fixing up that and removing the links in the PKGBUILD (though I did this out of preference) the game started working for me. So if zdoom has difficulty finding zdoom.pk3, you need to edit that .ini mentioned earlier and change all the directory lines from gzdoom to zdoom.
Not sure if this is a personal problem from previous installations or whatever, just posting in case someone else encounters this.
Comment by grubber
This is the recommended version for ZDoom. FMOD Ex does not have stable API and ZDoom compiles only with some versions of it. Even if you successfully compiled ZDoom with the fmodex package from the community repo, it would break and have to be recompiled every time the fmodex package is updated.
Comment by stevenhoneyman
does this specifically need to depend on that version of fmodex? (there's a newer one in the main repos)
Comment by alucryd
grubber: having SVN version in the pkgdesc of a git package isn't exactly correct.
Comment by grubber
The way makepkg does automatic pkgver updates has changed (see http://allanmcrae.com/2012/08/changes-to-vcs-packaging-support-in-makepkg/), hence the error.
Anyway, the latest revision does not compile successfuly for me, so I'm waiting until it does before updating the package.
Comment by LunaVorax
This package isn't getting the latest version of ZDoom.
PKGBUILD is set to grab the r4207 while r4294 is available.
Comment by Toney
ZDoom code license:
Code original to ZDoom is under the 3-point modified BSD license. (http://zdoom.org/wiki/License)
Anonymous comment
I am a robot. It is recommended to keep files in $pkgname/, instead of deep nesting. Suggestion: use "makepkg --source". This robot will not bother you again.
Comment by grubber
Updated. Included fmodex lib in the package, as it's not API compatible between versions and updates to the fmodex package (which is now in community repo) break compilation/sound in zdoom. Also cleaned up the PKGBUILD and fixed all errors reported by namcap.