From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Recipes relation tree
Date: Sun, 6 Dec 2009 12:05:13 -0700 [thread overview]
Message-ID: <20091206120513.235ea20a@xora.org.uk> (raw)
In-Reply-To: <ac9c93b10912061051j6826faiaa2f3fcbdd5b850b@mail.gmail.com>
On Sun, 6 Dec 2009 19:51:21 +0100
Frans Meulenbroeks <fransmeulenbroeks@gmail.com> wrote:
> 2009/12/6 Graeme Gregory <dp@xora.org.uk>:
> > On Sun, 6 Dec 2009 13:17:16 +0100
> > Frans Meulenbroeks <fransmeulenbroeks@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.
Graeme
next prev parent reply other threads:[~2009-12-06 19:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 6:42 Recipes relation tree FQ | Jaume Ribot
2009-12-01 7:25 ` Denys Dmytriyenko
2009-12-01 8:25 ` Sebastian Spaeth
2009-12-01 9:21 ` Koen Kooi
2009-12-01 19:40 ` Denys Dmytriyenko
2009-12-02 7:05 ` Sebastian Spaeth
2009-12-02 11:49 ` Marc Olzheim
2009-12-06 12:17 ` Frans Meulenbroeks
2009-12-06 14:54 ` Graeme Gregory
2009-12-06 18:51 ` Frans Meulenbroeks
2009-12-06 19:05 ` Graeme Gregory [this message]
2009-12-06 19:37 ` Frans Meulenbroeks
2009-12-06 19:49 ` Graeme Gregory
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091206120513.235ea20a@xora.org.uk \
--to=dp@xora.org.uk \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox