Having read http://www.freedesktop.org/wiki/Software/libinput/ which stateslibinput is a library to handle input devices in Wayland compositors  and to provide a generic X.Org input driver. It provides device  detection, device handling, input device event processing and  abstraction so minimize the amount of custom input code compositors  need to provide the common set of functionality that users expect.I am confused. I very much hope that the above means libinput is something new, which should mean that nothing of this horrible keyboard layout settings related to X.Org will be carried over to X.Org.I am confused by the mentioning of X.Org as X.Org input driver?Does this mean rathera) that the something from X.Org, i.e. an input driver, is brought to Wayland orb) that Wayland (or libinput) will provide some backward support, so that it would be able to forward input events to a X.Org server running as a client inside of Wayland?A good way to know this, would be to know how keyboard layouts are implemented in Wayland (I hope very much not as overly complicated as in X.Org)Disclaimer/Update:Since there was a down-vote. This question should not imply that being related to X.Org server is negative. It should simply help out to understand where to put this library.
Is (wayland's) libinput something new, i.e., not related to X.Org server?
xorg;keyboard;wayland
Yes, libinput is something new that started as a part of the wayland project to be used instead of the x11 input drivers (like xorg-evdev and xorg-synaptics and xorg-wacom and so on and so forth).In answer to your a/b scenario, it would be b, that is that libinput is not dependent on wayland and thus can run on other display servers (like X or Mir) as well.