[Openembedded-architecture] Recipe Specific Sysroots

[Trevor Woerner]

In theory, if more resources were directed towards fixing the issues found in
Martin's "Failed dependencies..." logs (e.g.
http://lists.openembedded.org/pipermail/openembedded-core/2016-November/128521.html)
would your proposal be necessary?

On Mon 2016-11-28 @ 06:11:39 PM, Richard Purdie wrote:
> Known issues/Todo:
> * Once a dependency is installed into a recipe specific sysroot, it 
>   can't be removed. In particular, if you rebuild that dependency (and 
>   its sstate checksum changes), it isn't reinstalled.

If I'm building and image that includes recipeA, and recipeA DEPENDS on
recipeB, then in recipeA's sysroot I will find artifacts from both recipeA and
recipeB?

But if I then bump the version of, or tweak the recipe for, recipeB, will
recipeA's sysroot be updated to include the newer version of recipeB before
recipeA gets rebuilt?

Will my final image include recipeA artifacts that have been rebuilt against
the new recipeB? I assume my final image will include the updated recipeB's
artifacts?