Re: [PATCH 0/1 V2] bitbake-whatchanged: print what is about to happen

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

On Friday 10 August 2012 11:47:38 Robert Yang wrote:
> Changes of V2:
> 
> * Fix a typo fn -> 'fn'
> 
> * Use "bitbake -e" rather than "bitbake -e recipe" to get the BB_STAMPS_DIR
> 
> * Use "BB_STAMPS_DIR=<path> bitbake -S recipe" to regenerate the stamps
> 
> * Change the summary format a little, now it looks like:
>   - (without -v):
>     === Summary: (3653 changed, 1927 unchanged)
>     Newly added: 807
>     PV changed: 48
>     PR changed: 276
>     Depends changed: 2522
> 
>   - (with -v):
>     === Summary: (3653 changed, 1927 unchanged)
>     Newly added: 807
>     Depends changed: 2846
> 
> // Robert
> 
> The following changes since commit 2dec760b79bb7e2e79c33c5127fa64685bd86a18:
> 
>   foomatic: fix perl path for target (2012-08-08 10:06:00 +0100)

So leaving Chris's objections aside for a moment, I applied this and the 
BB_STAMPS_DIR change, and ran the script on my build directory which is out of 
date with respect to the metadata (i.e. metadata has been updated since the 
last build). The output seems to suggest that no changes have been made, which 
is not the case:

----------- snip -----------
$ bitbake-whatchanged core-image-minimal
Figuring out the BB_STAMPS_DIR ...
Generating the new stamps ... (need several minutes)

=== Summary: (0 changed, 0 unchanged)
Newly added: 0
PV changed: 0
PR changed: 0
Depends changed: 0
----------- snip -----------

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre