unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: Julien Lepiller <julien@lepiller.eu>, help-guix@gnu.org
Subject: Re: List build dependencies of a store item
Date: Wed, 23 Oct 2019 21:52:49 +0530	[thread overview]
Message-ID: <cu71rv38m92.fsf@systemreboot.net> (raw)
In-Reply-To: <61E5568F-D054-4080-A075-E21B534B1CA8@lepiller.eu>

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


> I think a store item doesn't know where it comes from, so you can only
> find its runtime references.

That's a good point. I missed that.

> If you have a package foo, you can find its build-time dependencies
> with guix graph:
>
> guix graph foo

Indeed, this is what I want but for a modified version of a package
defined in a file. I realized I could do it with

guix graph -e '(load "/path/to/file.scm")'

However, it might be nicer to have something like

guix graph -f /path/to/file.scm

similar to

guix build -f /path/to/file.scm

> There's even a script that was shared here to show the path between
> two nodes of a guix graph, but I can't find it anymore.

Yes, I remember such a script too. It would be very useful to have. But,
even I am unable to find it. If someone knows where to find that script,
please share a link.

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

  reply	other threads:[~2019-10-23 16:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23  5:33 List build dependencies of a store item Arun Isaac
2019-10-23  6:31 ` Julien Lepiller
2019-10-23 16:22   ` Arun Isaac [this message]
2019-10-23 16:49     ` Gábor Boskovits
2019-10-23 20:19       ` Arun Isaac
2019-10-23  8:04 ` Efraim Flashner
2019-10-23 16:27   ` Arun Isaac

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=cu71rv38m92.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=help-guix@gnu.org \
    --cc=julien@lepiller.eu \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).