[OE-core] [PATCH 1/1] dump_cache.py: Move it from bitbake

Robert Yang liezhi.yang at windriver.com
Wed Sep 12 08:51:08 UTC 2018



On 09/12/2018 04:43 PM, Richard Purdie wrote:
> On Wed, 2018-09-12 at 16:27 +0800, Robert Yang wrote:
>> Add it to oe-core can make it's easier to use, e.g., we don't need
>> use
>> /path/to/bitbake/contrib/dump_cache.py to run it, just use
>> dump_cache.py after
>> the build is initialized.
>>
>> Signed-off-by: Robert Yang <liezhi.yang at windriver.com>
>> ---
>>   scripts/dump_cache.py | 95
>> +++++++++++++++++++++++++++++++++++++++++++++++++++
>>   1 file changed, 95 insertions(+)
>>   create mode 100755 scripts/dump_cache.py
> 
> Since the script is heavily tied to bitbake itself, I don't think this
> change makes sense. The name is also too generic just to insert into
> PATH (dump which cache?).
> 
> We could move it within bitbake I guess but I have to ask the question,
> how many people really need to run this and is the location therefore a
> real problem? Any user needing this can like adjust their PATH or
> figure out the right path to the script easily enough?

I guess seldom people really uses it since seldom people cares the internal
of the cache. I'm fine to leave it in bitbake, let's drop the patch, thanks.

// Robert

> 
> Cheers,
> 
> Richard
> 



More information about the Openembedded-core mailing list