this game received an update from 1.3.1302 to 1.3.1.1304 please note: - the numbering scheme is wrong in regard to portage ordering - some mods don't work with this version (e.g doom3-lms will complain with 'wrong dll version'), but will install because of a wrong DEPEND proposed by PaulBredbury in thread: http://forums.gentoo.org/viewtopic-p-3887102.html#3887102 Reproducible: Always
Created attachment 110366 [details] games-fps/doom3-1.3.1.1304
It breaks mods because id messed up their own numbering scheme. I'd recommend ignoring this update, because of the numbering mess and mod breakage. Hopefully id will release a new version, with a sane version number that actually increments.
Well, it's been a while and no sign of Id releasing a better versioned patch. Any ideas here? I *could* do the whole "add new version, mask old version" trick that I had to do early on in the doom3 cycle (again, thanks to Id naming/versioning), but I think it is ugly, and really isn't workable if it breaks mods.
My vote is to completely ignore it. It cannot be a "proper" release if doom3 itself says on its "update" screen that 1.3.1302 is "up-to-date". If I were a conspiracy theorist, I'd say that iD have deliberately sabotaged this release (whose primary advantage is Vista compatibility for the game without any mods) because they hate Microsoft's attempted crippling of OpenGL in Vista, and yet have pressure to release a Vista-compatible version :) Some scraps of info here, to add to the mystery: http://lms.d3files.com/forum/viewtopic.php?t=2364
this patch isn't ignorable for Doom3 mod developers running Gentoo. Doom3 1.3 doesn't compile with GCC 4.0. I kept the latest GCC 3 around on my system just for compiling Doom 3 DLLs, but that option has caused some head aches. Doom3 1.3.1 compiles with GCC 4, and this is the biggest reason to update. By now, most mods have upgraded to 1.3.1 anyhow.
Created attachment 120268 [details] doom3-1.3.1.1304.ebuild Tidied ebuild.
Could put doom3-1.3.1.1304 into Portage, package-masked. It does not work with doom3-cdoom (bug #167558), doom3-lms, or doom3-opencoop (bug #161656), which are the biggest Doom3 mods. The error is: Sys_Error: wrong game DLL API version
(In reply to comment #7) > Could put doom3-1.3.1.1304 into Portage, package-masked. It does not work with > doom3-cdoom (bug #167558), doom3-lms, or doom3-opencoop (bug #161656), which > are the biggest Doom3 mods. > > The error is: Sys_Error: wrong game DLL API version > that boggles my mind. I moved a Doom3 project from 1.3 to 1.3.1 and there was minimal changes to make. It impacts large and small mods the same, so... these doom3 projects are just being lazy ;-)
In which folder should I put the ebuild? I tried 'doom3-1.3.1.1304' but that didn't work.
(In reply to comment #9) > In which folder should I put the ebuild? I tried 'doom3-1.3.1.1304' but that > didn't work. > o_O in a local overlay, .../overlay/games-fps/doom3/
*** Bug 179699 has been marked as a duplicate of this bug. ***
Created attachment 121449 [details] doom3-1.3.1.1304.ebuild Added "dedicated" USE flag, to keep games-mods.eclass happy.
Any ideas when this is going to be committed guys?
(In reply to comment #13) > Any ideas when this is going to be committed guys? > dont hold your breath. it's hard enoughto get *anything* committed.
Created attachment 154525 [details] doom3-1.3.1304.ebuild Accoding to ID Software on http://zerowing.idsoftware.com/linux/doom, doom3-linux-1.3.1.1304.x86.run contains DOOM III 1.3.1, build 1304. So, it might be correct to rename the ebuild to doom3-1.3.1304.ebuild.
in portage
