gtk+ in dependency graph for qt

  • Done
  • quality assurance status badge
Details
4 participants
  • Efraim Flashner
  • Ludovic Courtès
  • Maxim Cournoyer
  • Ricardo Wurmus
Owner
unassigned
Submitted by
Efraim Flashner
Severity
normal
E
E
Efraim Flashner wrote on 1 Jun 2017 08:14
(address . bug-guix@gnu.org)
20170601061439.GB2884@macbook42.flashner.co.il
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.

--
Efraim Flashner <efraim@flashner.co.il> ????? ?????
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEkVdB/rIvpOM7bo+N9MHTkX6s7pMFAlkvsMgACgkQ9MHTkX6s
7pO0EQ/9F4aR7ou+ltFRK46nX8W4zl28E2uA4bLuGqaLRlJeqz4yguiQrl4Prs/Q
bvE9Hje0gve2ZOCOVvE3HIeP82ofjOX5CXJ5/k3a9AyRSDvrQuBAqIkk2372cOCc
H/H1Wg/bMwdaGI4xPv6uTPdptvuVditfd3E9KXTgjnIFeEU3Wb6f3x1uJQE30C41
Vn8HPh4gtkZnQ3KKsdwtzXGBkR3C6cWnVcL7pV1fUPFtTSynfxZh6kxTfCJQuQvz
t2bMAFpcAU73XpSKYe293qEVPeXBSSvk4y2C7b8s8PB0wKQGhd1DT6d1ECmxT+Mf
51iiX+2kjpsW1IgHG5dK0eV6rxpEeoHLa7bbAAKVD6YUKDRNq0gcOW7ui81JWEbM
x5OrD5JUA7qqhEWF8xIf2GX0Zc+j3c62oQqnxTQp5/XLiiVXKHT98Ffh5wzBGQG5
GwMXpkv7ZtjM9LFdLq8EYojFJxKqZwfxJdg/NXYHvA07ZDJg3qqdhTA/lgl5iu1j
u8sdv0OxwaLzmnKnNs9laeSf0MI0gh2Ox/BebRNzmIn8xFsrNu+ABnBh8C37Ofej
/oCWP5W63mFaU1KKjF+iC8UCFDdrG3EKtJcitNWZ9hTTNcnQnPA5BPap1Tl9I2SS
Xli+BCn66MxC+XKfU4qBg2Uk4F+/3dUBEFH9DSxuwOqC0XEgKDs=
=9YKj
-----END PGP SIGNATURE-----


E
E
Efraim Flashner wrote on 2 Jul 2017 19:27
(address . 27179@debbugs.gnu.org)
20170702172722.GA2938@macbook42.flashner.co.il
On Thu, Jun 01, 2017 at 09:14:40AM +0300, Efraim Flashner wrote:
Toggle quote (6 lines)
> 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.

--
Efraim Flashner <efraim@flashner.co.il> ????? ?????
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAllZLPkACgkQQarn3Mo9
g1HA4RAAmxA6Mt3MuJJfztNOEBuswrG8GhbBdm7xOCTjY7B60ZfHXIyZ9XjXbmy1
GgIEMKkNXrvboLbDXMD/hygySHcHaxkn0APlaJdPfR8/Lae3U76l+6a5ELNevKYv
82Ur9Lb98hSFlLBpwOv4i2wG26BWx6/1/whuY032Ve1svj+94iQecY10jXddvzQE
hIBHzBHn6aio02zZRA+flKJACyMbgzzdz1Hp7Ba0B0yyDa1ItvoK+6m0YiY4EPah
6cptc/+tlhd62cfv87ToXa/OGPXI8Fxee0Ssu1q5vddNlD6wOtOdw7B14Xu6ZFgX
JJZUbnb1xYJKSmY55dja5yBXTMSzW7rb7IPexVvDNyk5t/Qn+DqlHf3wP9s0AnMs
DBuoWGDJsGHnN7TOl/xvalZw/hPUj1xp5jRXpIPYlVg+dcYPY5tgcvImrdn1KX++
BAzf4wxAIzxJYYG3JH+lbZsclT+BK9H2a1ppEtqJLDRdP8WRIg/qYYIf2021Bn5g
pVnvNkdsYJH5jhkb8QIW35Mea/VCUTXfO6xcBvDqFjxdLn2iI07l87wML1vnHXuf
Y8cx4/R6oHhluGavCfEpuav/slSoqJkCemHoRyrjYUN2l5QiPRYoIjL8TxYY/4hg
WmbXqsujFTgHke0fX+FmKsy3vMBah0Tl8LsT26iAPGmWw/UvTys=
=WahP
-----END PGP SIGNATURE-----


R
R
Ricardo Wurmus wrote on 2 Jul 2017 21:23
(name . Efraim Flashner)(address . efraim@flashner.co.il)(address . 27179@debbugs.gnu.org)
87d19iiqwv.fsf@elephly.net
Efraim Flashner <efraim@flashner.co.il> writes:

Toggle quote (10 lines)
> 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?

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
E
E
Efraim Flashner wrote on 2 Jul 2017 22:16
(name . Ricardo Wurmus)(address . rekado@elephly.net)(address . 27179@debbugs.gnu.org)
20170702201632.GE2938@macbook42.flashner.co.il
On Sun, Jul 02, 2017 at 09:23:44PM +0200, Ricardo Wurmus wrote:
Toggle quote (16 lines)
>
> Efraim Flashner <efraim@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.

--
Efraim Flashner <efraim@flashner.co.il> ????? ?????
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAllZVJgACgkQQarn3Mo9
g1FjZA/+PEyxfH902XoQVEVjnZ+BBGNiSc6znTB+/XQxA/IasQ1J712Drc6/jS1N
omitUJmXxKGgn42AtL+9kLQe0GqCWuz01qp/nYNXFGcAuAu5Sto2sYZVVIlh6g2s
1bnJE/d3hwo9DDE5DheRqo8VjgZkWCcKPYRwW+KX7JGjyH7GqWr7JBsJqQAV415y
J5AiSTP9YmJpHzPHupP9SsmM6PfTLknSgDyz51st2WNj5od2mxmNT/6MoWgCBnnH
BS6HMMoKJguOqAOLF7FTaTdYlRBUKxXTg5dIPZX39HZoHUCgMVNha8hshkN0hcs9
wPXLAFfepGuoMZX7xno5nHP8iV3RAPK3ONByFF8dyX+y5Uf/+pg/o1M8uGHBdq05
PDu3PllUTHs8V/SV8Au6dm0e6vKVMG4mZXSSEE1GMn1JX20XQ7QP+RUcirWE+G5x
nvm7qCovFZzZf9godpiw5VWs5nvAgTAQs51Cosr5fGGTsxcj8g/5kdbPigf4uHuU
0VGwB0XY/fyfeL6AppqnH0019WjtrJB0ix8QGTplmhzWXkoaDjqv9K3095YuQidc
JE6hHb5gxahrXcxNeNZF1Qe7Twt7T1/Acmovt+5AtmpwFSlKftJfQZIjp2m9MZbc
LHcdwIaoTAmrueZsiymxyrLHPEWRsHr5nBvEQnkyDu8Tpk3uZ38=
=mZo3
-----END PGP SIGNATURE-----


E
E
Efraim Flashner wrote on 10 Aug 2017 19:36
(name . Ricardo Wurmus)(address . rekado@elephly.net)(address . 27179@debbugs.gnu.org)
20170810173644.GB11046@macbook42.flashner.co.il
On Sun, Jul 02, 2017 at 11:16:32PM +0300, Efraim Flashner wrote:
Toggle quote (23 lines)
> On Sun, Jul 02, 2017 at 09:23:44PM +0200, Ricardo Wurmus wrote:
> >
> > Efraim Flashner <efraim@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.


--
Efraim Flashner <efraim@flashner.co.il> ????? ?????
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAlmMmawACgkQQarn3Mo9
g1HTjBAAtBWm7ZVRsBsoieYc9qIsUj/qmhu3+DbdXLvPBZ6Y5DFxOr/TBaFKbHJn
lQysIINBbmxFhOdYx60M3/FXwdWoBRQk2fspgNSPyHbC8M95K5uEvn0FAy41ekhJ
B/nqWFrxULjmYsSTFexsqloVZbuBMGQKW7FaW+/pjncHHwRdivSTM6ph2PMuk6E5
5mSSvjTyKSyv1EQfEPb12OSTayb8F+Hn+xAVr4+Hv8w5H3+TgZmRp6AYj5YlTqV1
W4g+/QikWrS+8Mm1daJgIaFgMaCFmXgTzCgqBPTifhkrkNlMcA3IsmYoKRZwyMcF
25fNjydRLgKKGwInFgBb2CUcZToWFZjLIhEsBSmCOkfk6rP9W2tMCELmT1hHGkR3
OVNfSSZ1Fq0UAQtm2K/QzljXr4XrfsigmwneANJsPDopDGAJ/GDz7e99XZy17F5h
HiBF1Zt5qm0BXVNTbgW7QtfiAwLyhtVzohftMlLtjOmEWbImDg689/rpzpvpwgVC
9l1CtMZINPbM0kVrP3o7UwlWWWT85sb+TP+upQWNhzQdj4Dp0/lTNsvDRLoQBUOD
yJI38KkNr2Pjhix1dxC6Um5mBtU50t3fSl6SXqei7RmmNab6fPsow3fjKI3loRAW
ssQh2G/oN3R971xwHnZIIflVgKRKQ+otzV1TE+whV23BjosiSgc=
=vhVs
-----END PGP SIGNATURE-----


L
L
Ludovic Courtès wrote on 22 Aug 2017 10:15
(name . Efraim Flashner)(address . efraim@flashner.co.il)
87h8x0dnn2.fsf@gnu.org
Efraim Flashner <efraim@flashner.co.il> skribis:

Toggle quote (28 lines)
> 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 <efraim@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+:

Toggle snippet (7 lines)
$ grep -r 8f5bm9zqakgl7mc4lr5ck8l91vhlzv85 /gnu/store/4p4vw5shvj1ywjy91m5q3mpjyr1wp1hx-libwacom-0.25
/gnu/store/4p4vw5shvj1ywjy91m5q3mpjyr1wp1hx-libwacom-0.25/bin/libwacom-list-local-devices:export XDG_DATA_DIRS="/gnu/store/s0mc7alnzxpvvfay3pcpw8n3ipcq0a0r-shared-mime-info-1.8/share:/gnu/store/1k9zfb8wqd3pm97jsiy8n5szy56hgn8k-glib-2.52.2/share:/gnu/store/8f5bm9zqakgl7mc4lr5ck8l91vhlzv85-gtk+-3.22.15/share${XDG_DATA_DIRS:+:}$XDG_DATA_DIRS"
/gnu/store/4p4vw5shvj1ywjy91m5q3mpjyr1wp1hx-libwacom-0.25/bin/libwacom-list-local-devices:export GTK_PATH="/gnu/store/8f5bm9zqakgl7mc4lr5ck8l91vhlzv85-gtk+-3.22.15/lib/gtk-3.0${GTK_PATH:+:}$GTK_PATH"
$ ldd /gnu/store/4p4vw5shvj1ywjy91m5q3mpjyr1wp1hx-libwacom-0.25/bin/.libwacom-list-local-devices-real |grep
gtk

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.

Thoughts?

Ludo’.
M
M
Maxim Cournoyer wrote on 21 Nov 2021 05:54
(name . Efraim Flashner)(address . efraim@flashner.co.il)(address . 27179-done@debbugs.gnu.org)
87y25icdmy.fsf@gmail.com
Hello,

Efraim Flashner <efraim@flashner.co.il> writes:

Toggle quote (5 lines)
> 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.

Apologies for not seeing this earlier, but I fixed it with commit
206193fec9cf527dec73841c16b6ae6ae52aaf37 last June.

Now, we should ensure gtk@4 doesn't depend on qtbase though... (see
#51994).

Closing,

Thanks!

Maxim
Closed
?