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.y...@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? Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
