bug#30710: guix graph gives duplicate nodes

2018-03-12 Thread Ludovic Courtès
Hello, Hartmut Goebel skribis: > On Fri, 09 Mar 2018 23:59:26 +0100 l...@gnu.org (Ludovic Courtès) wrote: >> >>> Good catch! I implemented what you suggest above in commit >>> 464f5447396fcec9b43f7eab71d5d42b522a157f. > > Thanks, this solved the issue only partially: On my "kde-plasma" branch:

bug#30710: guix graph gives duplicate nodes

2018-03-10 Thread Hartmut Goebel
On Fri, 09 Mar 2018 23:59:26 +0100 l...@gnu.org (Ludovic Courtès) wrote: > >> Good catch! I implemented what you suggest above in commit >> 464f5447396fcec9b43f7eab71d5d42b522a157f. Thanks, this solved the issue only partially: On my "kde-plasma" branch: $ ./pre-inst-env guix graph plasma-worksp

bug#30710: guix graph gives duplicate nodes

2018-03-09 Thread Ludovic Courtès
Björn Höfling skribis: > If you look into gnu/packages/autotools.scm, you see that > autoconf-wrapper is not a package, but a package-factory: > > (define* (autoconf-wrapper #:optional (autoconf autoconf)) > > Now the package definitions of "automake" and "libtool" each use the > same fragment of

bug#30710: guix graph gives duplicate nodes

2018-03-09 Thread Björn Höfling
On Wed, 07 Mar 2018 16:18:51 +0100 l...@gnu.org (Ludovic Courtès) wrote: > Hello, > > Hartmut Goebel skribis: > > >> This is expected. Strictly speaking, we’re talking about two > >> different package objects, hence the different IDs. > > > > I wonder > > > > a) whether it is useful to have

bug#30710: guix graph gives duplicate nodes

2018-03-07 Thread Ludovic Courtès
Hello, Hartmut Goebel skribis: >> This is expected. Strictly speaking, we’re talking about two different >> package objects, hence the different IDs. > > I wonder > > a) whether it is useful to have different graph nodes for the same package. > > This is about usability of the resulting graph,

bug#30710: guix graph gives duplicate nodes

2018-03-06 Thread Hartmut Goebel
Hi, > This is expected. Strictly speaking, we’re talking about two different > package objects, hence the different IDs. I wonder a) whether it is useful to have different graph nodes for the same package. This is about usability of the resulting graph, esp. since this is the default graph outp

bug#30710: guix graph gives duplicate nodes

2018-03-05 Thread Ludovic Courtès
Hello, Hartmut Goebel skribis: > "guix graph" delivers the same package with different IDs. Here is an > example with a node delivered twice. (For plasma-workspace, which I'm > working on, this package was even listed four times). > > $ ./pre-inst-env guix graph -t package -b graphviz qtbase | g

bug#30710: guix graph gives duplicate nodes

2018-03-05 Thread Hartmut Goebel
Hi, "guix graph" delivers the same package with different IDs. Here is an example with a node delivered twice. (For plasma-workspace, which I'm working on, this package was even listed four times). $ ./pre-inst-env guix graph -t package -b graphviz qtbase | grep autoconf-wrapper   "59511552" [lab