Using build history
When maintaining software for an embedded product, you need a way to know what has changed and how it is going to affect your product.
On a Yocto system, you may need to update a package revision (for instance, to fix a security vulnerability), and you need to make sure what the implications of this change are; for example, in terms of package dependencies and changes to the root filesystem.
Build history enables you to do just that, and we will explore it in this recipe.
How to do it...
To enable build history, add the following to your conf/local.conf file:
INHERIT += "buildhistory"
The following enables information gathering, including dependency graphs:
BUILDHISTORY_COMMIT = "1"
The preceding line of code enables the storage of ...
Get Embedded Linux for Developers now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
