Ludovic Courtès schreef op do 23-06-2022 om 22:20 [+0200]:
> Hi,
> 
> Josselin Poiret <dev@jpoiret.xyz> skribis:
> 
> > This reduces their total closure, since libinput pulls in gtk+ which
> > adds roughly 400MiB.
> 
> Good catch; applied, thanks!
> 
> It never occurred to me that it could depend on GTK+; apparently that’s
> for some debugging GUI, but it’s not clear how it’s supposed to get
> invoked:
> 
> [...]
> 
> What’s is it used for?

FWIW, it has a man page:
<https://man.archlinux.org/man/extra/libinput/libinput-debug-gui.1.en>?

I did some quick searches for 'libinput-debug-gui' on the Web but
didn't find any uses in the wild, so maybe we don't really lose
anything by disabling it?

Also, having multiple library variants is a bit messy (there was some
bug involving multiple versions of cairo used by a single app?), so I'd
prefer to eliminate the libinput / libinput-minimal distinction (maybe
with a separate libinput-debug-gui package if desired?).

Greetings,
Maxime.