Any reason 50-joystick-all.conf is not installed by the ebuild? It seems that this file can be installed as-is after # UNCOMMENT TO ENABLE HOTPLUGGING OF JOYSTICKS
Ping?
Maybe if you submit a patch for the ebuild it will go faster.
Created attachment 334000 [details] xf86-input-joystick-1.6.1.diff Ebuild patch attached.
Ok for the src_install() part, but not for patching 50-joystick-all.conf. If you want the latter changed, take it to upstream.
The patch uncomments the lines marked with # UNCOMMENT TO ENABLE HOTPLUGGING OF JOYSTICKS # Driver "joystick" # MatchIsJoystick "on" # MatchDevicePath "/dev/input/event*" I don't see what this has to do with upstream. If you want xf86-input-joystick installed with hotplugging by default, uncomment the lines. If not, don't. Other packages have hotplugging enabled by default. E.g.: xf86-input-synaptics, xf86-input-vmmouse. Since users in Gentoo usually install packages on their own, I don't see how hotplugging can hurt.
I.e., hotplugging in this context means not having to fiddle with xorg.conf to enable support for the device. Since Xorg moves to not having xorg.conf at all, that's the only reasonable choice.
1.6.1-r1 now installs the configuration snippet to /usr/share/X11/xorg.conf.d Regarding the modifications of 50-joystick-all.conf, we are not keen on carrying patches that have not been accepted upstream, so you will have to get it merged there first.
As maintainer of xf86-input-joystick I recommend not enabling it without explicit user consent because most users have the input module installed "accidentially" (by default, all input modules, global joystick useflag or whatever pulls that in) without knowing what it is good for or even that they have it installed. Because the module is usually installed by default, I decided it to not harm the usual usecase of a joystick: playing games. Disabling a feature when you don't know what provides it, is not fun. E.g. Ubuntu has it enabled by default and when you enter the right keywords in google, all resources are about uninstalling the module. Besides that, the default configuration probably doesn't suit most people anyway, so they already need to edit the configuration file. Better provide the relevant documentation to the user after installing the ebuild.
(In reply to comment #8) > Because the module is usually installed by default, I decided it to not harm > the usual usecase of a joystick: playing games. Disabling a feature when you > don't know what provides it, is not fun. E.g. Ubuntu has it enabled by > default and when you enter the right keywords in google, all resources are > about uninstalling the module. I had no idea that's the case -- agreeing with you then. Thanks for replying on this bug.
