**** BEGIN LOGGING AT Fri Jan 22 02:59:58 2021
Jan 22 12:08:46 <mort> Is there a way to figure out why bitbake builds a particular package for an image?L
Jan 22 12:09:55 <mort> I tried to show the dependency graph with -g, but that's so huge (`bitbake -g <package>` produces 8700 lines of graphviz dot file) that I don't have the hardware necessary to make a readable graph out of it
Jan 22 12:10:49 <mru> grep the output for the package you're interested in
Jan 22 12:11:22 <mru> or do it the rude way, delete/block the offending package and see what it complains about
Jan 22 12:11:41 <mort> haha, that would work
Jan 22 12:12:44 <mort> a "print the part of the graph which results in this package being included" command would be useful though
Jan 22 12:13:06 <mru> maybe there is one and I haven't found it
Jan 22 13:00:51 <rburton> sounds like you want oe-depends-dot
Jan 22 13:01:02 <rburton> but i'm a fan of just blacklisting the recipe and seeing what breaks :)
Jan 22 15:57:25 <armpit> looks like oe is getting soft
**** ENDING LOGGING AT Sat Jan 23 02:59:57 2021