Switching From Evdev/Synaptics Drivers To Libinput On X.Org

[darkbasic]

Looks like it's there for me, just in a slightly different spot than where you expected it. I hate to venture here, because of the anticipated discussion side-effects, but I thought libinput was going to be dependent on systemd-logind. I don't see that, at least in this version. Nor do I see anything about it in the linked libinput pages.

With evdev you need both dev-libs/libevdev and x11-drivers/xf86-input-evdev. This is the same per libinput, but there is no x11-drivers/xf86-input-libinput.

[emblemparade]

It's good news to see libinput adopted in X and in Mir. As others have pointed out, we'll all benefit from combining efforts on a single input library for Linux.

The "funny" thing is that the Mir project originally had one justification for the need to break from Wayland as bad input handling for mobile, but are now adopting libinput...

[phred14]

With evdev you need both dev-libs/libevdev and x11-drivers/xf86-input-evdev. This is the same per libinput, but there is no x11-drivers/xf86-input-libinput.

Odd thing is that in addition to there being no x11-drivers/xf86-input-libinput, I see no mention of libinput in either weston or wayland ebuilds. The more recent weston ebuilds have a hard-coded "--disable-libinput-backend" flag with no use_enable.

There appears to be no use for libinput in portage, at least not yet.

[GreatEmerald]

Ah, there's already a bug and a prototype ebuild for that: https://bugs.gentoo.org/show_bug.cgi?id=532566

[V10lator]

Ah, there's already a bug and a prototype ebuild for that: https://bugs.gentoo.org/show_bug.cgi?id=532566

I just wanted to point you to that, glad you found it. There's also a thread at the gentoo forums for people interrested in it: http://forums.gentoo.org/viewtopic-t...ighlight-.html - Both, the bug report and the thread are started by me.

For now, there's also some functionality missing from libinput

While that's true there's also at least one function in libinput missing in libevdev: Taking the (default) CPI from udev. When you know how that works you're able to overwrite the default CPI (currently udev can't detect a CPI switch). This makes it possible to use a high-CPI mouse without any mouse acceleration and without having a ultra-fast mouse that you can't really handle anymore.