Recipes relation tree

Recipes relation tree

[FQ | Jaume Ribot]

Hi all,

Is there any way to obtain a kind of visual "dependency tree" between 
recipes? Sometimes is dificult to follow-up dependencies, when 
rebuilding individual packages.

Thanks.

-- 
Jaume Ribot Caner

Re: Recipes relation tree

[Denys Dmytriyenko]

On Tue, Dec 01, 2009 at 07:42:33AM +0100, FQ | Jaume Ribot wrote:
> Hi all,
>
> Is there any way to obtain a kind of visual "dependency tree" between 
> recipes? Sometimes is dificult to follow-up dependencies, when rebuilding 
> individual packages.

Have you looked at -g option of bitbake?

  -g, --graphviz        emit the dependency trees of the specified packages in
                        the dot syntax

-- 
Denys

Re: Recipes relation tree

[Sebastian Spaeth]

[-- Attachment #1: Type: text/plain, Size: 410 bytes --]

Denys Dmytriyenko wrote:
> Have you looked at -g option of bitbake?
> 
>   -g, --graphviz        emit the dependency trees of the specified packages in
>                         the dot syntax

A related question. This generates depends.dot just fine, but I found a
reference to rdepends.dot in some manual. I would be very much
interested in an RDEPENDS tree, is there a way to get this?

spaetz


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]

Re: Recipes relation tree

[Koen Kooi]

On 01-12-09 09:25, Sebastian Spaeth wrote:
> Denys Dmytriyenko wrote:
>> Have you looked at -g option of bitbake?
>>
>>    -g, --graphviz        emit the dependency trees of the specified packages in
>>                          the dot syntax
>
> A related question. This generates depends.dot just fine, but I found a
> reference to rdepends.dot in some manual. I would be very much
> interested in an RDEPENDS tree, is there a way to get this?

If you use testlab.bbclass you get one for each image.

regards,

Koen

Re: Recipes relation tree

[Denys Dmytriyenko]

On Tue, Dec 01, 2009 at 09:25:05AM +0100, Sebastian Spaeth wrote:
> Denys Dmytriyenko wrote:
> > Have you looked at -g option of bitbake?
> > 
> >   -g, --graphviz        emit the dependency trees of the specified packages in
> >                         the dot syntax
> 
> A related question. This generates depends.dot just fine, but I found a
> reference to rdepends.dot in some manual. I would be very much
> interested in an RDEPENDS tree, is there a way to get this?

Actually it does generate both.

-- 
Denys

Re: Recipes relation tree

[Sebastian Spaeth]

Denys Dmytriyenko wrote:
>> A related question. This generates depends.dot just fine, but I found a
>> reference to rdepends.dot in some manual. I would be very much
>> interested in an RDEPENDS tree, is there a way to get this?
> 
> Actually it does generate both.

Interesting, here with bitbake 1.8 I definitely only get
	depends.dot  task-depends.dot

Is this only in 1.10, or am I missing a secret config option?

spaetz

Re: Recipes relation tree

[Marc Olzheim]

[-- Attachment #1: Type: text/plain, Size: 594 bytes --]

On Wed, Dec 02, 2009 at 08:05:39AM +0100, Sebastian Spaeth wrote:
> Denys Dmytriyenko wrote:
> >> A related question. This generates depends.dot just fine, but I found a
> >> reference to rdepends.dot in some manual. I would be very much
> >> interested in an RDEPENDS tree, is there a way to get this?
> > 
> > Actually it does generate both.
> 
> Interesting, here with bitbake 1.8 I definitely only get
> 	depends.dot  task-depends.dot
> 
> Is this only in 1.10, or am I missing a secret config option?

The rdepends are the lines in depends.dot with '[style=dashed]'.

Marc

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: Recipes relation tree

[Frans Meulenbroeks]

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.

FM

Re: Recipes relation tree

[Graeme Gregory]

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

Re: Recipes relation tree

[Frans Meulenbroeks]

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.

Frans

Re: Recipes relation tree

[Graeme Gregory]

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

Re: Recipes relation tree

[Frans Meulenbroeks]

2009/12/6 Graeme Gregory <dp@xora.org.uk>:
> 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.
>

Ah ok, forgot that bitbake -g world would give me the complete graph <blush>

Thanks, FM

Re: Recipes relation tree

[Graeme Gregory]

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

> 2009/12/6 Graeme Gregory <dp@xora.org.uk>:
> > 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.
> >
> 
> 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