Description: Program to test device events (keyboard)... some kind of `xev`, but with direct access to the events... The package (well, a single C source code file) is part of "The Linux Console Project" (http://linuxconsole.sourceforge.net/), but it has been distributed as is, multiple times, on mailing lists and websites, as it is useful to test keyboard events... (and there is no published package for "The Linux Console Project"...). I used the SourceForge CVS HTTP access, but it might be cleaner to properly package the file, if it can be hosted somewhere...
Created attachment 83183 [details] app-admin/evtest-1.23.ebuild
Created attachment 83184 [details] evtest-1.23.c (the "package") I upload the source code file here, just in case... (and as it is tiny) Note you'll have to rename it to "evtest.c?rev=1.23", if you use the current ebuild... As said, it would probably be better to package the file... (but it might not be the place to discuss this in depth ^_^)
dev-util/joystick is a collection of http://linuxconsole.cvs.sourceforge.net/linuxconsole/ruby/utils and evtest is part of that.
err, games-util/joystick
(In reply to comment #3) > dev-util/joystick is a collection of > http://linuxconsole.cvs.sourceforge.net/linuxconsole/ruby/utils > > and evtest is part of that. > Ok then, but the ebuild should be renamed. From the package homepage, listed in the ebuild (http://atrey.karlin.mff.cuni.cz/~vojtech/input/): "The Linux Input Driver project is a project that replace the current handling of keyboards, mice and joysticks in Linux". I can understand it might more commonly be used for joysticks, but the package is more general than this (officially, I mean). Maybe something like "linux-input-driver-utils", I don't know (it's a bit long, but it's more or less the official name...). It should also be moved to "app-misc", as it is not specific to gaming (the description also will have to be generalized to all input devices). I will not reopen this report, nor create a new one, because of lack of time, but people will not be able to find this tool, if the package is named arbitrarily.
