Package Details: gzdoom 4.14.0-1

Git Clone URL: https://aur.archlinux.org/gzdoom.git (read-only, click to copy)
Package Base: gzdoom
Description: Feature centric port for all Doom engine games
Upstream URL: http://www.zdoom.org/
Licenses: GPL3, BSD, LGPL3
Replaces: gzdoom-legacy, gzdoom1
Submitter: None
Maintainer: xente
Last Packager: xente
Votes: 167
Popularity: 2.25
First Submitted: 2009-02-22 22:28 (UTC)
Last Updated: 2024-12-18 19:14 (UTC)

Dependencies (27)

Sources (4)

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 Next › Last »

Fincer commented on 2015-02-06 02:30 (UTC)

Thank you for informing me about the GIT version you already have available here. Well, let me clarify: The current PKGBUILD script grabs correct gzdoom version from Github. However, the problem is that if pure tar.gz archive is used, gzdoom doesn't recognize version number correctly, leading to <unknown version> issue. [fincer@fincer-laptop fincer]$ gzdoom GZDoom <unknown version> - - SDL version Compiled on Feb 6 2015 Using video driver x11 And this is what I refer to when talking about "messes with version numbering". I asked GZDoom developer Graf Zahl about this issue and he stated: "Do you have the git command line utilities installed? The broken version number suggests you have not. With this you can also retrieve the source for any branch or tag, including the release versions." Doing the installation by suggested git way gets the version number shown correctly in the program, too. Regardless of available tar.gz archives in Github. That's why I think git way is the only correct way to install this package - unless you want <unknown version> to be visible while running the program. Otherwise, the current compilation script works very fluently and builds gzdoom version 2.0.04 as suggested in the AUR package title. As you already said.

grubber commented on 2015-02-04 21:36 (UTC)

The PKGBUILD doesn't mess with anything, it uses only what is provided in the release tarball. If you want to build from git, you should use <https://aur.archlinux.org/packages/gzdoom-git/>.

Fincer commented on 2015-02-04 00:05 (UTC)

At the moment PKGBUILD messes with GZDoom version numbering, resulting to a <unknown version>. Instead of using tar.gz package (which is presented in the current PKGBUILD file), the package must be built with git method. I corrected the PKGBUILD file for those who want the correct GZDoom version number shown when launching the program. See fixed PKGBUILD file for GZDoom 2.0.04 + all versions 1.8.5 and above here: http://forum.drdteam.org/viewtopic.php?f=22&t=6524&p=56382#p56382

<deleted-account> commented on 2014-09-25 08:22 (UTC)

If the first link for gm.sf2 is not work, use this link: https://app.box.com/s/ewa6p5d21rf9uly6ator

grubber commented on 2014-09-24 21:11 (UTC)

Updated to 2.0.03. See also <https://aur.archlinux.org/packages/gzdoom1/> for 1.8.7. zanny: You can report bugs at <http://forum.drdteam.org/viewforum.php?f=24>.

zan commented on 2014-09-22 01:14 (UTC)

So yeah, a lot of breakage in gz 2.0 with the Mesa drivers: By default, it is using a compatibility profile and does not recognize core profiles supporting 3.3, so it just says "get GL 3.3". If you override the Mesa version string with 3.3, it tries to use GLSL 4.0 shaders. If you use the arg -gl3 to force 3.3, it fails to compile some fragment shader. And I can't even find the gzdoom bug tracker. It isn't off their github repo and my google-fu is failing me.

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 Next › Last »