[oe] strange error: missing depends...

[Justin Patrin]

On 6/1/07, Richard Purdie <rpurdie at rpsys.net> wrote:
> On Fri, 2007-06-01 at 07:55 -0700, Justin Patrin wrote:
> > In the spirit of giving users more info, I've noticed that lately
> > OE/bitbake will compile all of the packages and only start the
> > do_package_write once almost everything is built, before the image I'm
> > targeting gets built.
> >
> > I've figured out that this is due to dependency handling as what
> > depends on the packages being written to disk is the creation of the
> > image, which installs from those packages. The packaging also seems to
> > happen if I directly bitbake a provider. It seems somewhat strange
> > that bitbaking something which depends on something else doesn't cause
> > the dependency to create its package...
>
> If A DEPENDS on B and you want A (you bitbake A), do you need the
> package from B? The answer is you don't, you only need B to stage.
>

This is true, DEPENDS is just build. What I really meant was RDEPENDS.

> The dependency chains tell bitbake when it needs to build the package
> and it only does thinsg which it needs.
>
> This is totally configurable. You could add something to local.conf
> which always caused dependent packages to build if you so wished...
>

I understand this all and I also understand how and why bitbake is
doing what it's doing. My observation was that the common user
expectation, IMHO, is that doing: "bitbake nano" will build the nano
ipk(s) and all ipks of all RDEPENDS so that it is immediately
installable.

I would also expect that *any* package built, including DEPENDS would
be packaged as well but this is of lesser consequence.

Perhaps this expectation is only due to my use of previous bitbake/OE
iterations which always did this. If bitbake is not going to package
for all built recipes I'd suggest that this information be added to
the manual next to informaiton on how to make it build the packages
(hopefully via another command instead of adding a dependency to
local.conf...).

> Add some details about the options to the bitbake manual is on my todo
> list and is one reason I've not made the imminent bitbake release.
>

:-)

-- 
Justin Patrin