Tracking image, package, and SDK contents
The easiest way to ensure we have the image, packages, and software development kit (SDK), along with the expected contents, is to use the buildhistory mechanism.
When a recipe is updated for a new version or has its code changed, it may influence the contents of the generated packages and, consequently, the image or SDK.
Poky deals with many recipes and images or SDKs frequently have tens or hundreds of packages. Therefore, it may be challenging to track the package contents. The Poky tool that helps in this task is buildhistory.
buildhistory, as the name suggests, keeps a history of the contents of several artifacts built during the use of Poky. It tracks package, image, and SDK building and their contents.
To enable buildhistory in our system, we need to add the following lines of code in our build/conf/local.conf file:
Figure 10.1 – How to enable buildhistory support
The INHERIT method includes...
