summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/packagegroups
diff options
context:
space:
mode:
authorAlexander Kanavin <alex.kanavin@gmail.com>2023-10-17 15:30:50 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2023-10-19 13:26:05 +0100
commit15b08b82347d0909d3c0498b437a17b19ddf6a3f (patch)
treefa974ce6fe9e235d4aa00b1d20bed059cabe0538 /meta/recipes-core/packagegroups
parent62739c2e8f4006cafb9d8c83a9221033b7c0243d (diff)
downloadpoky-15b08b82347d0909d3c0498b437a17b19ddf6a3f.tar.gz
scripts/bitbake-whatchanged: remove
This is not documented or tested, and indeed hasn't been producing useful reports for some time. The script works by redirecting STAMPS_DIR into a separate location, then running bitbake -S none, then comparing the two sets of stamp filenames with regexes: Match the stamp's filename group(1): PE_PV (may no PE) group(2): PR group(3): TASK group(4): HASH stamp_re = re.compile("(?P<pv>.*)-(?P<pr>r\d+)\.(?P<task>do_\w+)\.(?P<hash>[^\.]*)") Then there's some code that finds out what changed in the above between the two sets. Messing about with STAMPS_DIR like that isn't supported, and will either do nothing, or remove the original stamps. Also stamp filenames aren't really a 'public API'. For finding out the changes between two builds, 'bitbake -s printdiff' is a supported and tested option. It may be a bit too verbose, but that can be more easily fixed than rewriting bitbake-whatchanged into a working state. (From OE-Core rev: f8193978eb0944e693e6a5cfbf9035e104e489f0) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core/packagegroups')
0 files changed, 0 insertions, 0 deletions