Buildhistory

[Paul Eggleton <paul.eggleton@linux.intel.com>]

Hi all

[Sorry for the cross-post but I thought this would be worth talking about in 
all three of the lists. By way of discussions and other threads some of you 
may already be aware of buildhistory - if so you can skip this message.]

With buildhistory.bbclass (which incorporates and extends functionality 
previously provided in OE-Classic via testlab.bbclass) we now have the ability 
to record some useful information about the output of a build, and commit this 
information into a git repository so that changes over time can be examined 
and highlighted. The information recorded includes the content and size of 
each package, content and size of images (at the package and file level), etc.

A side-benefit of buildhistory is that it can also be used just to get 
information about the content of your image including dependency graphs, so 
you can figure out exactly what pulled in some particular package.

Further information can be found here:

 https://wiki.yoctoproject.org/wiki/Buildhistory

If you are doing a recipe upgrade or making a change to the metadata that 
might have wide-ranging effects on the output, then you should consider using 
buildhistory to determine whether or not there are any issues.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre