10:23 whot: rahl: xinput list-props <device name> will tell you which driver is active, should be the libinput one, but the various prefixes will tell you.
16:19 rahl: whot: cheers
16:57 wlb: weston Merge request !1275 opened by Daniel Stone (daniels) CI: Add Debian 12 (bookworm) jobs https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1275 [CI]
23:02 riteo: hiiii!
23:03 riteo: I need your help here because I can't find anything satisfactory. Should I worry about globals appearing and disappearing in real time? Also, should I delete all "child" objects created by a now-removed global?
23:05 riteo: The thing becomes annoying when I have a list of seat data and I have to iterate it all at every seat-related thing. Perhaps I shouldn't care about aknowledging every single seat?
23:15 riteo: I'm pretty much in the situation outlined by https://gitlab.freedesktop.org/wayland/wayland/-/issues/291
23:17 riteo: I'm in a position to either overengineer handling for the removal of globals that should _usually_ stay or ignore it outright. If a specification doesn't say anything regarding something the compositor may do anything pretty much.
23:20 riteo: ...just noticed that in the ticket linked above someone says that if clients have indeed done that we can't rollback. I guess I'll have just to deal with it?