From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Lirzin <mthl@openmailbox.org>
Cc: Guix-devel <Guix-devel@gnu.org>
Subject: Re: New ‘guix graph’ command
Date: Thu, 27 Aug 2015 13:26:37 +0200 [thread overview]
Message-ID: <87io812cr6.fsf@gnu.org> (raw)
In-Reply-To: <87egipgfr3.fsf@openmailbox.org> (Mathieu Lirzin's message of "Thu, 27 Aug 2015 12:58:08 +0200")
Mathieu Lirzin <mthl@openmailbox.org> skribis:
> Nice job, It is really convenient to have such utility.
>
> Does it sound feasible to produce different edge colors depending of the type
> of inputs?
Of course! But this is left as an exercise to the reader. :-)
Similarly, I thought we could use different color boxes based on the
size of a store item, for the ‘references’ DAGs.
It “just needs” adding an attribute argument to the ‘emit-node’ and
‘emit-edges’ hooks of <graph-backend>. I don’t plan to work on it in
the near future but would definitely welcome patches.
> Not really important, but IMO it would be clearer to define bag-emerged
> in terms of what bag is doing with something like this.
>
> ‘bag’
> This is the package DAG, _including_ implicit inputs.
>
> ‘bag-emerged’
> Similar to ‘bag’, but this time without all the bootstrap
> dependencies.
>
> For instance, the following command:
>
> guix graph --type=bag-emerged coreutils | dot -Tpdf > dag.pdf
>
> [...]
>
> What do you think?
Perhaps this isn’t very clear but I wanted to list the graph types in
order of increasing complexity, which is why ‘bag’ comes after
‘bag-emerged’. Dunno if something needs to be changed; thoughts?
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-08-27 11:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 22:53 New ‘guix graph’ command Ludovic Courtès
2015-08-27 9:25 ` Pjotr Prins
2015-08-27 10:58 ` Mathieu Lirzin
2015-08-27 11:26 ` Ludovic Courtès [this message]
2015-08-27 15:15 ` Alex Kost
2015-08-27 15:20 ` Leo Famulari
2015-08-27 15:34 ` Thompson, David
2015-08-27 20:55 ` Ludovic Courtès
2015-08-27 21:01 ` Thompson, David
2015-09-03 20:32 ` Andreas Enge
2015-09-03 20:46 ` Ludovic Courtès
2015-09-03 20:54 ` Thompson, David
2015-09-03 20:55 ` Cook, Malcolm
2015-09-04 8:13 ` Pjotr Prins
2015-09-04 9:49 ` Andreas Enge
2015-09-11 0:02 ` Cyril Roelandt
2015-09-11 7:19 ` Leo Famulari
2015-09-11 12:26 ` Ludovic Courtès
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=87io812cr6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=Guix-devel@gnu.org \
--cc=mthl@openmailbox.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).