Nope but if you find a non intrusive way, I’ll take it :-) I just mv things around at post-install time. A few gnome ports do this.
— Antoine > On 4 Nov 2023, at 17:51, Rafael Sadowski <raf...@sizeofvoid.org> wrote: > > On Thu Nov 02, 2023 at 11:59:24AM +0100, Antoine Jacoutot wrote: >>> On Thu, Nov 02, 2023 at 10:10:22AM +0000, Stuart Henderson wrote: >>> On 2023/11/02 07:56, 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. >>> >>> Would it be worth keeping a list of these ports in comments in the Makefile >>> for wayland/libinput-openbsd so we can find them more easily (for testing >>> or reenabling later)? >> >> That would be nice, yes! >> >> > > Hi Antoine, > > okay i can live with that. Do you have any idea how to override the > install (prefix) in your meson module? > > Cheers, Rafael >
