You are not logged in.

#1 2014-07-02 11:26:37

dice
Member
From: Germany
Registered: 2014-02-10
Posts: 413

pacgraph image differs from console output

Hi,
I am not exactly sure where to ask, so I put this into Newbie Corner.

When I run pacgraph, I get this image.
2eaqj9c.png

As you can see, there is for example libreoffice-common on the picture.

But when I run pacgraph in console mode libreoffice-common is not in the list.
Same thing happens to the linux package too, so I guess it happens for even more packages.

Is this the intended behaviour of pacgraph or is this a bug?


I put at button on it. Yes. I wish to press it, but I'm not sure what will happen if I do.  (Gune | Titan A.E.)

Offline

#2 2014-07-02 12:00:09

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,456
Website

Re: pacgraph image differs from console output

I don't use pacgraph much, but I did just confirm something similar happens here.

The image creation from pacgraph reported "Placing 344 nodes"

But then the console version only listed 138 packages.  This is very close, but not identical to pacman's -Qet output which lists 137 explicitly installed packages that are not required by anything else.  Grabbing these lists and `diff'ing them indicates that pacgraph -c shows all of these plus ttf-droid (which is explicitly installed, but also required by mplayer).

Pacman -Qe, in contrast give 186 results - far more than pacgraph -c, while `pacman -Qq` gives 601.

It would seem the console output of pacgraph might be *intended* to list only packages that were explicitly installed and not required by any other packages, though it doesn't seem to do that perfectly either.

The graph itself, I have no idea where that comes from - but perhaps it plots only packages over some minimum threshold of size (total speculation).


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

Board footer

Powered by FluxBB