From: zimoun <zimon.toutoune@gmail.com>
To: Phil <phil@beadling.co.uk>, help-guix@gnu.org
Subject: Re: Output all dependencies recursively for package
Date: Sun, 31 Jan 2021 20:09:57 +0100 [thread overview]
Message-ID: <861re0gby2.fsf@gmail.com> (raw)
In-Reply-To: <85zh0pdzyn.fsf@beadling.co.uk>
Hi Phil,
On Sun, 31 Jan 2021 at 12:59, Phil <phil@beadling.co.uk> wrote:
> I'm looking for a recursive list of all bar@version given package
> foo?
>
> Something like:
> guix show --recursive-dependencies foo
>
> Giving:
> dependencies: bar@version, some-dependency-of-bar@version
I proposed something like that:
<http://issues.guix.gnu.org/issue/43477>
adding a «backend» to “guix graph”. In my mind, it was exactly the use
case you are describing with the option to select the “type” of the
graph. It has been “rejected” (not the word, but too lazy to find the
adequate one), mainly because I just wanted to list all the nodes
(topologically sorted or not) and Ludo and Ricardo raised that it is not
about “graph”. Anyway.
Maybe it could go to “guix show”. However, the current implementation
of “guix show” uses “guix package --show=”, literally. And adding more
things in “guix package” does not seem a good idea, IHMO.
In other words, instead of use (guix scripts package) in (guix scripts
show), do the contrary. I have a patch that do that but never
submitted because I have never felt the need or time to. Anyway.
With the current tools, “guix refresh --list-transitive” maybe is enough
for your needs. Note that the returned packages are not necessary the
ones you can access at the CLI level, for instance ’gcc’.
Hope that helps,
simon
prev parent reply other threads:[~2021-01-31 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 12:59 Output all dependencies recursively for package Phil
2021-01-31 15:03 ` Joshua Branson
2021-02-01 1:32 ` Tobias Geerinckx-Rice
2021-02-01 6:26 ` zimoun
2021-02-01 16:21 ` me--- via
2021-02-01 19:36 ` Phil
2021-01-31 15:30 ` Efraim Flashner
2021-01-31 19:09 ` zimoun [this message]
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=861re0gby2.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=phil@beadling.co.uk \
/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).