First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 127174
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Games <games@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Lars Wendler (Polynomial-C) <polynomial-c@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
doom3-1.3.1302-r1.ebuild.diff doom3-1.3.1302-r1.ebuild.diff patch Lars Wendler (Polynomial-C) 2006-03-22 04:47 0000 1.19 KB Details | Diff
doom3-data-1.1.1282.ebuild.diff doom3-data-1.1.1282.ebuild.diff patch Lars Wendler (Polynomial-C) 2006-03-22 04:48 0000 704 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 127174 depends on: Show dependency tree
Bug 127174 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-03-22 04:45 0000
Hi,

I emerged doom3 this way:

echo "games-fps/doom3 cdinstall" >> /etc/portage/package.use
emerge doom3

Everything emerged fine but after that when the game is started it asks for two
CD-keys. The one for the original Doom3 game and one for the Doom3 Resurrection
of Evil expansionpack. But I don't own the expansionpack, only the original
game. So I can't enter the second key and am unable to play the game.
The solution is quite simple to just remove the folder /opt/doom3/d3xp with all
its content but I think this should be handled by the ebuild so that the d3xp
folder only gets installed when the user asks for it. Maybe with a useflag?

I changed the games-fps/doom3 and games-fps/doom3-data ebuilds a little bit to
get the desired behavior. I'll attach two diffs to show you what I did.

Cheers
Poly-C

------- Comment #1 From Lars Wendler (Polynomial-C) 2006-03-22 04:47:18 0000 -------
Created an attachment (id=82857) [details]
doom3-1.3.1302-r1.ebuild.diff

added "roeexpansion" useflag

------- Comment #2 From Lars Wendler (Polynomial-C) 2006-03-22 04:48:10 0000 -------
Created an attachment (id=82858) [details]
doom3-data-1.1.1282.ebuild.diff

added "roeexpansion" useflag

------- Comment #3 From Chris Gianelloni (RETIRED) 2006-03-22 07:12:18 0000 -------
I've added the "roe" USE flag in CVS... I guess I never noticed this because I
actually had installed RoE on my older ebuild and had already entered the key. 
Thanks for the information and the patches.

------- Comment #4 From Paul Bredbury 2006-03-22 12:26:38 0000 -------
I don't think this is right - I think the only problem was that doom3-data
should not contain the line:
cp ${Ddir}/base/pak000.pk4 ${Ddir}/d3xp

Because d3xp/pak000.pk4 is the one and only RoE file.

Note that doom3-linux-1.3.1302.x86.run installs d3xp/game0{1,2,3}.pk4 and
d3xp/pak001.pk4 without asking about RoE, so I believe we should do the same.
Which means that a "roe" USE flag is not required.

I'll check some more, then file a bug with patches.

Background info:
http://zerowing.idsoftware.com/linux/doom/

------- Comment #5 From Lars Wendler (Polynomial-C) 2006-03-22 13:21:48 0000 -------
Even when the original installer installs all these files into d3xp folder the
result is the same. The game is unplayable for everybody who doesn't own the
RoE expansionpack until the d3xp folder gets deleted.
So I think it's no problem when the ebuild handles this for the user via
useflag (or maybe a seperate RoE-ebuild if this is the cleaner solution).

Poly-C

------- Comment #6 From Chris Gianelloni (RETIRED) 2006-03-22 13:25:14 0000 -------
That could very well be.  I know that removing all of d3xp doesn't hurt the
original game, which was why I just went ahead with it.  I also need to add an
ebuild for doom3-roe anyway, I just haven't had the time.

------- Comment #7 From Paul Bredbury 2006-03-22 16:13:18 0000 -------
(In reply to comment #5)
> Even when the original installer installs all these files into d3xp folder the
> result is the same. The game is unplayable for everybody who doesn't own the
> RoE expansionpack until the d3xp folder gets deleted.

WORKSFORME (I've created bug #127244 as a result), and I'd expect to see lots
of angry Linux gamers otherwise :)  Check that d3xp/pak000.pk4 does not exist,
and try renaming ~/.doom3/

As well as having played Doom 3 installed from ebuilds (without RoE being
installed) for a few months with a few popular mods (such as the ones that have
recently entered Portage), I just performed this test:

What I did:
Rename ~/.doom3/
Unmerge all installed doom3 ebuilds so that /opt/doom3 does not exist
emerge doom3 with -cdinstall and -roe USE flags
Confirm that the /usr/local/games/doom3 (installed by running
doom3-linux-1.3.1302.x86.run) tree matches /opt/doom3, with the only exceptions
being bash wrappers "doom3" and "doom3-dedicated" having moved to
/usr/games/bin (with "doom3-dedicated" renamed to "doom3-ded").
emerge doom3 with cdinstall USE flag
start doom3, enter cd key, start single-player game - OK
click on "mods" in main menu, and see only "Doom 3"
exit doom3, confirm that the only files in /opt/doom3/d3xp are: 
game0{1,2,3}.pk4 and pak001.pk4
start doom3, join a multiplayer Internet server game - notice that it says the
doom3 cd key is OK, and the RoE cd key is "N/A".
emerge doom3 with additional "roe" USE flag, and watch it install
d3xp/pak000.pk4
start doom3, enter RoE cd key, see additional "d3xp" under "mods", select it,
start RoE single-player game - OK

First Last Prev Next    No search results available      Search page      Enter new bug