[bitbake-devel] [PATCH] cooker: Drop package-depends.dot and pn-depends.dot generation

[Peter Kjellerstedt]

> -----Original Message-----
> From: Paul Eggleton [mailto:paul.eggleton at linux.intel.com]
> Sent: den 25 januari 2017 20:17
> To: Richard Purdie
> Cc: bitbake-devel at lists.openembedded.org; Peter Kjellerstedt
> Subject: Re: [bitbake-devel] [PATCH] cooker: Drop package-depends.dot
> and pn-depends.dot generation
> 
> On Wednesday, 25 January 2017 11:12:57 AM NZDT Richard Purdie wrote:
> > On Wed, 2017-01-25 at 11:05 +0000, Peter Kjellerstedt wrote:
> > > pn-dependes.dot when visualizing the dependencies between packages.
> > > Even though task-depends.dot is more complete, trying to render it
> > > is near impossible given the sheer number of nodes and edges it
> > > contains. Already visualizing pn-depends.dot is hard but possible
> > > with some gvpr and tred filtering. Here are some statistics from
> > > one of my typical builds:
> > >
> > >                         Nodes  Edges
> > >                         -----  ------
> > > pn-depends.dot           1183   12087
> > > package-depends.dot      5939   55615
> > > task-depends.dot        13756  125870
> > >
> > > As can be seen, the number of nodes and edges in task-depends.dot
> > > is a magnitude greater than in pn-depends.dot.
> >
> > Its certainly simpler, but the data is just plain buggy. I'm not sure
> > I'd trust anything those files told me, even if they are easier to
> > view.
> >
> > I appreciate task-depends is hard to load graphically, it is helpful
> > even as a text file though, I do use it a lot since its a near direct
> > dump of bitbake's internal parsed task dependencies.
> 
> What if we collapsed down task-depends.dot to PNs only in order to
> produce pn-depends.dot? Then at least it would be reasonably accurate.
> 
> Cheers,
> Paul

That would work for me at least.

//Peter