all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Why does slim-service-type depend on GTK+?
Date: Wed, 10 Jun 2020 12:01:47 +0200	[thread overview]
Message-ID: <87v9jzme7o.fsf@gnu.org> (raw)
In-Reply-To: <871rmnfjek.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Wed, 10 Jun 2020 09:51:31 +0200")


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


  reply	other threads:[~2020-06-10 10:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10  7:51 Why does slim-service-type depend on GTK+? Pierre Neidhardt
2020-06-10 10:01 ` Mathieu Othacehe [this message]
2020-06-10 12:20   ` Pierre Neidhardt
2020-06-10 12:51     ` Pierre Neidhardt
2020-06-11  7:37       ` Pierre Neidhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v9jzme7o.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.