]> code.ossystems Code Review - openembedded-core.git/commit
buildhistory_analysis: include related fields in output
authorPaul Eggleton <paul.eggleton@linux.intel.com>
Thu, 19 Jan 2012 10:32:12 +0000 (10:32 +0000)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 19 Jan 2012 14:59:16 +0000 (14:59 +0000)
commit2c5b90c6d1b1091779602ebe03e84674eb63ea83
tree74933f6c493a93d446bc348cc86957f565fee0dc
parentce6c80a1e68c2af0b4b5fa27582ad9c9f119e5c1
buildhistory_analysis: include related fields in output

Sometimes, when a value changes in the buildhistory it is useful to
know when a related (but not necessarily itself monitored) value
changes as it can help explain the change. For example, when the list
of installed packages for an image changes it could be caused by a
change to one of the image-related variables.

Related field changes are recorded as sub-items of each change.
Currently the only way to visualise these is via the buildhistory-diff
tool, so an example would be:

Changes to images/qemux86/eglibc/core-image-minimal (installed-package-names.txt):
  locale-base-de-de was added
  procps was added
  * IMAGE_LINGUAS: added "de-de"
  * IMAGE_INSTALL: added "procps"

Here we see that two additional packages have been added to the image,
and looking at the related changes to the two variables IMAGE_INSTALL
and IMAGE_LINGUAS we have the explanation as to why.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/lib/oe/buildhistory_analysis.py