Why does slim-service-type depend on GTK+?

Why does slim-service-type depend on GTK+?

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]

Hi Guix!

If I add the following service

--8<---------------cut here---------------start------------->8---
(service slim-service-type (slim-configuration
                                                 (display ":1")
                                                 (vt "vt8")))
--8<---------------cut here---------------end--------------->8---

to bare-bones.tmpl, it drags GTK+ in the closure.

Here is the slim-service-type definition:

--8<---------------cut here---------------start------------->8---
(define slim-service-type
  (handle-xorg-configuration slim-configuration
    (service-type (name 'slim)
                  (extensions
                   (list (service-extension shepherd-root-service-type
                                            slim-shepherd-service)
                         (service-extension pam-root-service-type
                                            slim-pam-service)

                         ;; Unconditionally add xterm to the system profile, to
                         ;; avoid bad surprises.
                         (service-extension profile-service-type
                                            (const (list xterm)))))

                  (default-value (slim-configuration))
                  (description
                   "Run the SLiM graphical login manager for X11."))))
--8<---------------cut here---------------end--------------->8---

Any idea how and why?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: Why does slim-service-type depend on GTK+?

[Mathieu Othacehe]

Hello Pierre,

> Any idea how and why?

Yes, you can use "guix graph" this way:

--8<---------------cut here---------------start------------->8---
mathieu@elbruz ~/guix-master [env]$ guix graph -t references /gnu/store/9pnnigbg2a173xxabfrb50mayw4la2ag-system --path /gnu/store/hh2z7mqlj54cs23a94afpxjgxfyda566-gtk+-3.24.14
/gnu/store/9pnnigbg2a173xxabfrb50mayw4la2ag-system
/gnu/store/bjsss7lbxzddqmljhvjjfczz3nrkpl32-boot
/gnu/store/zdfy15qp870amyi89irm4wrinmjfxgnw-shepherd.conf
/gnu/store/9znzaszxk0h9z7c13a12c6g5h7445rqb-shepherd-xorg-server-vt8.go
/gnu/store/kc3qblcylk8gywdfxjan40qffij6axqg-slim.cfg
/gnu/store/jjkn4f4xxiypjwkb2417xl2x34cx1rmn-startx
/gnu/store/53i1740vbpcmz19l7spvpy6h7vw4g2aj-X-wrapper
/gnu/store/8y45c5g3sxmks8kqjggwi099fabx2lqw-xserver.conf
/gnu/store/1mzxwf9hrs19zxahc3yqb25f3fravin6-xf86-input-libinput-0.28.2
/gnu/store/r0nhb1i210s1zrcgrckqr6kmdlrpyw6v-libinput-1.15.2
/gnu/store/hh2z7mqlj54cs23a94afpxjgxfyda566-gtk+-3.24.14
--8<---------------cut here---------------end--------------->8---

and find out how gtk ends-up in the closure :)

Thanks,

Mathieu

Re: Why does slim-service-type depend on GTK+?

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

Thanks Mathieu, this helps a lot indeed!

The slim service configuration depends on a generated startx, which
depend on this X-wrapper:

--8<---------------cut here---------------start------------->8---
(begin (setenv "XORG_DRI_DRIVER_PATH" (string-append "/gnu/store/8jn365r0kk69j1f4b1q2b7aa2qm1xvg1-mesa-19.3.4" "/lib/dri")) (setenv "XKB_BINDIR" (string-append "/gnu/store/7ar4wyrxbafj7x9ga1ycm5l01q82mw0m-xkbcomp-1.4.3" "/bin")) (let ((X (string-append "/gnu/store/kqibv2arki2dqkl0iczmz6rz0y7ff5vg-xorg-server-1.20.7" "/bin/X"))) (apply execl X X "-xkbdir" (string-append "/gnu/store/m96xy2wyfrg18m638h411k925rg8cjm6-xkeyboard-config-2.29" "/share/X11/xkb") "-config" "/gnu/store/jr40zgab1093hxikp3csp0wnk05v108l-xserver.conf" "-configdir" "/gnu/store/n98412kvx2jyj6k1xqj21iz22gmp0002-xorg.conf.d" (cdr (command-line)))))
--8<---------------cut here---------------end--------------->8---

So it seems that we can't remove mesa from the slim-service closure and
I guess that's expected.

Now xserver.conf drags the Xorg modules, which drags
xf86-input-libinput.

This one depends on libinput, but it also build with libinput-minimal.
Is this a mistake?
I'll test on my system with libinput-minimal and report.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: Why does slim-service-type depend on GTK+?

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 113 bytes --]

I confirm that xf86-input-libinput with libinput-minimal works.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: Why does slim-service-type depend on GTK+?

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 68 bytes --]

Patch sent: 41798.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]