On Thu, Nov 02, 2023 at 07:56:54AM +0100, Rafael Sadowski wrote:
> On Thu Nov 02, 2023 at 12:15:51AM +0100, Antoine Jacoutot wrote:
> > I don't understand all these patches against linux/input.h.
> > What is installing it and why?
> > If we don't want to use it, why do we have a port installing it?
> >
>
> linux/input.h is shipped with wayland/libinput-openbsd which is not
> hooked for now. I see here to points:
>
> - libinput-openbsd is not feature complete that the input works in a
> usable way in Wayland. There is still too little experience here.
>
> - sdl2 and gimp are good examples what happen if we hook
> wayland/libinput-openbsd. Ports will find linux/input.h and add new
> funtions to the port that are not tested.
>
> I would rather activate it right away, but we don't know how the
> applications will behave and if wayland/libinput-openbsd is stable so
> yet. This is the reason why we want to deactivate it first and then
> enable it step by step.
OK so that is because we consider libinput-openbsd non usable but we want to
enable it anyway.
I was confused, I though we wanted to add support for a working libinput
implementation.
You can go ahead, I will also make sure to patch it out everywhere I see it.
Thanks.
--
Antoine
No comments:
Post a Comment