Comment # 2 on bug 979554 from Stefan Dirsch

Just found an interesting upstream change for libinput and wacom driver.

libinput:
commit 3f569ec493e738242da97afe30f7dd2a3b2b834d
Author: Peter Hutterer <peter.hutterer@who-t.net>
Date:   Tue Apr 26 15:45:18 2016 +1000

    conf: rename to 60-libinput.conf

    60 sorts higher than the other drivers (evdev has 10, synaptics, wacom and
    others have 50) so we keep the same order.

    This is part of a two-step solution, the other half is renaming the
    xf86-input-wacom's config snippet to sort higher than libinput's.

    Currently libinput picks up devices that are (for now) destined to the
wacom
    driver. Since the wacom driver is more of a leaf package than libinput, the
    best option here is to make the wacom driver sort higher and let users
    uninstall it when not needed. To avoid crowding the 90-* space where users
    usually have custom config snippets, drop libinput down to 60 and bump
wacom
    up.

wacom:

commit 0da5cd545e38079b62656a23835c4943af05dc92
Author: Jason Gerecke <killertofu@gmail.com>
Date:   Wed Apr 27 10:10:27 2016 -0700

    conf: rename to 70-wacom.conf

    This is part of a two-step solution, the other half is renaming the
    xf86-input-libinput config snippet to sort lower than ours.

    Currently libinput picks up devices that are (for now) destined to the
wacom
    driver. Since the wacom driver is more of a leaf package than libinput, the
    best option here is to make the wacom driver sort higher and let users
    uninstall it when not needed. To avoid crowding the 90-* space where users
    usually have custom config snippets, libinput will drop down to 60 and
    wacom will bump up to 70.

    Fixes: https://sourceforge.net/p/linuxwacom/bugs/315/
    Fixes: https://github.com/linuxwacom/xf86-input-wacom/issues/4

Egbert, do you think it would make sense to do the same for synaptics snippet,
i.e. move from 50-synaptic.conf to 70-synapticts.conf? What should we do with
evdev idling on 10-evdev.conf?