Summary: | games-sports/vdrift ebuilds should have a force feedback USE flag | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | PhobosK <phobosk> |
Component: | [OLD] Games | Assignee: | Gentoo Games <games> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | mr_bones_ |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://wiki.vdrift.net/Setting_up_force_feedback | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | An ebuild that enables the force feedback in vdrift |
Description
PhobosK
2009-08-19 16:36:01 UTC
Created attachment 201717 [details]
An ebuild that enables the force feedback in vdrift
Added a ff USE flag to the original ebuild
Why would we just not always compile it with force_feedback=1? I guess I don't really see the point of having a use flag for it. (In reply to comment #2) Well since it is an option given by the upstream, probably we should comply with that. There are a number of ebuilds that do not allow the user to choose all the options upstream gives. I think it is wrong to decide instead of the user if an option should be turned on or off. Anyway my point was that this option should be turned on during compilation... with or without a force feedback USE flag... doesn't seem like there is a down side to just always compiling it in. In portage. |