Efraim Flashner <efr...@flashner.co.il> skribis:

> On Sun, Jul 02, 2017 at 11:16:32PM +0300, Efraim Flashner wrote:
>> On Sun, Jul 02, 2017 at 09:23:44PM +0200, Ricardo Wurmus wrote:
>> > 
>> > Efraim Flashner <efr...@flashner.co.il> writes:
>> > 
>> > > On Thu, Jun 01, 2017 at 09:14:40AM +0300, Efraim Flashner wrote:
>> > >> gtk+ is currently in the dependency tree for qt, but is not an input.
>> > >> Either we should add gtk+ as an input so the styling can be uniform
>> > >> between the two toolkits, or we should find which input pulls it in and
>> > >> see what other options we have for removing it from the graph.
>> > >>
>> > >
>> > > It appears that qtbase depends on libinput which depends on gtk+@3, and
>> > > also qtbase -> libinput -> libwacom -> gtk+@3.
>> > 
>> > Can we split libinput into a qt part and a separate gtk part?
>> > 
>> libwacom is built with glib-or-gtk-build-system, so if we switch
>> libinput to libinput-minimal then we can drop the GUI for libinput and
>> libwacom support and remove gtk+ as an input. Or we can try to build
>> libwacom without gtk.
> I just noticed that efl in elightenment.scm also has libinput as an
> input. I think for now we should replace both qtbase's and efl's
> libinput with libinput-minimal.

I guess you can reasonably start with EFL since it has few dependents.
I suppose we’ll also need a “libwacom-minimal” package no?

Or perhaps we should simply add a “lib” output since only the libwacom-*
commands depend on GTK+:

--8<---------------cut here---------------start------------->8---
$ grep -r 8f5bm9zqakgl7mc4lr5ck8l91vhlzv85 
$ ldd 
--8<---------------cut here---------------end--------------->8---

It’s not even clear that GTK+ is needed, given that it doesn’t show up
in ldd.

The same thing probably applies to libinput.



Reply via email to