Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 161608 - games-action/d2x-rebirth ~amd64 keyword request
Summary: games-action/d2x-rebirth ~amd64 keyword request
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Games (show other bugs)
Hardware: AMD64 Linux
: High enhancement
Assignee: AMD64 Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-11 19:57 UTC by Daniel Herzog
Modified: 2007-02-12 21:01 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Herzog 2007-01-11 19:57:35 UTC
Hi,

just installed d2x-rebirth on amd64 with worked without any problems.
I could play the first two levels without any problems, didnt test/play any further. Also multiplayer games and such things werent tested.
Anyway i feel like it should be hardmasked on amd64 just as it is on x86 since it worked flawlessly.

CFLAGS="-march=nocona -O2 -pipe" was used

Reproducible: Always

Steps to Reproduce:
Comment 1 Daniel Herzog 2007-01-11 20:27:11 UTC
Just tried to install d1x-rebirth with descent1-demodata and descent1-maps which worked when i turned the "demo" flag on, compiled without problems started and entered the game.
Without "demo" it produced the error mentioned at the end of the ebuild.
I just couldnt get the mouse working, which resulted my spaceship to rotate all day long. It worked with keyboard input.
I suggest hardmasking d1x-rebith for amd64 too, since the game is playable although with possible restrictions.
I do not know wether I could have used the -maps files, i found them nowhere in the menu of the game.
Comment 2 Simon Stelling (RETIRED) gentoo-dev 2007-02-12 18:42:08 UTC
Sorry, that's not good enough for ~amd64, and hardmasking doesn't make sense, because it's used for packages that were keyworded previously but don't work anymore/have security issues etc.
Comment 3 Daniel Herzog 2007-02-12 21:01:32 UTC
I dont quite understand the decision for d2x (I do for d1x, though).
The d2x ebuild has never been changed and is hardmasked since it is in the tree according to the changelog.
There even is a "# Should work on amd64 also" within the .ebuild and it did so for me...

(Please note comment #1 is about another (very similar) package)