unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Phil <phil@beadling.co.uk>
Cc: help-guix@gnu.org
Subject: Re: Output all dependencies recursively for package
Date: Mon, 01 Feb 2021 02:32:49 +0100	[thread overview]
Message-ID: <87zh0oh8se.fsf@nckx> (raw)
In-Reply-To: <87v9bdno7b.fsf@dismail.de>

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

Phil,

Phil <phil@beadling.co.uk> writes:
> I'm looking for a command similar to 'guix show' which will give 
> a packages explicit
> dependencies, recursively.

Best ditch the d-word; it's too ambiguous to be useful, as 
illustrated by this thread.

If by ‘explicit dependencies’ you mean all explicitly listed 
inputs then none of the suggested commands so far actually do what 
you're asking for, which is to show nothing for, e.g., the ‘hello’ 
package.

I don't think there's a CLI command to do so, but it's quite easy 
to recurse over all (package-{,native-,propagated-}inputs pkg) 
using ‘guix repl’ if you know some Scheme.  What's your use case 
here?

Perhaps it's good enough to warrant ‘guix refresh 
--list-transitive-inputs’ (to avoid philosophical discussions 
about what constitutes a graph :-).

Kind regards,

T G-R

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

  reply	other threads:[~2021-02-01  1:33 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 [this message]
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

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=87zh0oh8se.fsf@nckx \
    --to=me@tobias.gr \
    --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).