[oe] Recipes relation tree

[Graeme Gregory]

On Sun, 6 Dec 2009 20:37:30 +0100
Frans Meulenbroeks <fransmeulenbroeks at gmail.com> wrote:

> 2009/12/6 Graeme Gregory <dp at xora.org.uk>:
> > On Sun, 6 Dec 2009 19:51:21 +0100
> > Frans Meulenbroeks <fransmeulenbroeks at gmail.com> wrote:
> >
> >> 2009/12/6 Graeme Gregory <dp at xora.org.uk>:
> >> > On Sun, 6 Dec 2009 13:17:16 +0100
> >> > Frans Meulenbroeks <fransmeulenbroeks at gmail.com> wrote:
> >> >
> >> >> It would also be nice to be able to get the used by information.
> >> >> E.g. if I change a package (especially wrt staging) I would
> >> >> like to verify that the packages which use the modified package
> >> >> still build.
> >> >>
> >> >> The current el-cheapo solution for a package XYZ is to do
> >> >> something like a grep  DEPENDS.*XYZ */*.bb but of course that
> >> >> won't work if DEPENDS spans multiple lines.
> >> >>
> >> > bitbake -g target will drop a dependency graph in the directory
> >> > you run bitbake from.
> >> >
> >> > Graeme
> >>
> >> Graeme, I know but I would like to have exacty the reverse: a list
> >> of packages that depend on the package at hand.
> >> bitbake -g gives all packages a package depends on, but I would
> >> like to have a list of packages that depend on a specific package.
> >>
> >> so e.g. I want to get a list of packages that depend on libxml (and
> >> bitbake -g libxml gives me the packages libxml depends on).
> >>
> >> I hope that clarifies my question.
> >>
> > Still the same answer, bitbake -g world then parse the graph.
> >
> 
> Ah ok, forgot that bitbake -g world would give me the complete graph
> <blush>
> 
> Thanks, FM
> 

Then put the script you use to parse the graph in contrib/ and enjoy
eternal fame for solving one of OEs FAQs.

Graeme