From: "Gábor Boskovits" <boskovits@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: List build dependencies of a store item
Date: Wed, 23 Oct 2019 18:49:15 +0200 [thread overview]
Message-ID: <CAE4v=pj4h2cXEynxm88AXQUGSgYHVzvLr3WD5VHfBRB=hkeFEQ@mail.gmail.com> (raw)
In-Reply-To: <cu71rv38m92.fsf@systemreboot.net>
Hello,
Arun Isaac <arunisaac@systemreboot.net> ezt írta (időpont: 2019. okt. 23.,
Sze, 18:43):
>
> > 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.
>
The script is here:
https://lists.gnu.org/archive/html/guix-devel/2018-07/msg00212.html
--
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21
next prev parent reply other threads:[~2019-10-23 16:49 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
2019-10-23 16:49 ` Gábor Boskovits [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=pj4h2cXEynxm88AXQUGSgYHVzvLr3WD5VHfBRB=hkeFEQ@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=arunisaac@systemreboot.net \
--cc=help-guix@gnu.org \
/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.