[oe] How does oe handle rebuilds?

[C Michael Sundius]

I think there are different policies that you can use to decide re building
dependent
packages...

I added a patch to our bitbake that creates a "black-list" of packages that
should be checked for decencies that have out of date time stamps.

this is different to what exists in bitbake since it currently uses a "white
list"
which becomes a list of packages that don't need to be checked. I found
that you'd have to select a lot of packages for that to be useful. most of
the
time people are developing on a finite number of packages which you might
need to rebuild.

attached is a diff to the bitbake that we're currently using (its version is
1.11 or something)
I hope its useful (I'd love for it to be put into bitbake, alas it slipped
through the cracks
last time I pointed it out to the list).

I'm adding bitbake-dev on this list since *I think* this is a bitbake thing.

mike





On Mon, Mar 7, 2011 at 9:58 AM, Charles Manning <cdhmanning at gmail.com>wrote:

> I find I often have problems when using oe that changing a recipe does
> not result in dependent packages being rebuilt. A bit of Googling
> suggests that many experience this issue and take manual steps to
> force rebuilding.
>
> For example, changing the kernel requires rebuilding various libraries
> (tslib etc) and rebuilding the image.
>
> 1.Should oe be able to handle that automatically or is this oe's
> "killer defect" (ie. opposite of "killer feature").
> 2. Is there something missing in recipes to show the correct dependencies?
> 3. What is the best way to manage these stale dependencies?
>
> Thanks
>
> Charles
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bitbake-blacklist.diff
Type: text/x-patch
Size: 2151 bytes
Desc: not available
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20110307/df937181/attachment-0002.bin>