Re: New ‘guix graph’ command

[Ludovic Courtès]

Mathieu Lirzin <address@hidden> 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’.