[bitbake-devel] [PATCH] cooker: bitbake memres server should not always reload the cache

[Paul Eggleton]

On Friday 28 March 2014 07:56:43 Jason Wessel wrote:
> On 03/28/2014 06:43 AM, Alex Damian wrote:
> > Please hold merging this change.
> > 
> > I think we need to discuss a bit on this. My expectation is that the
> > Bitbake server will reinit its state between builds, re-parsing the
> > configuration files and reload the cache. I am not sure why we would
> > consider maintaining the hot cache copy in memory between builds.
>
> It is about increasing the interactivity of the system.  There are certainly
> times you need to soft reset, but perhaps that is what we need to expose. 
> If I want to run a dev shell and have done a build, this is something I'd
> like to be instantaneous, or if I am working on the package and want to
> re-run the compile and package steps, there really is no need to parse.
> 
> There is a trade off for the individual package work vs the work of
> rebuilding the entire image.  In the case of the entire image you most
> certainly want the soft reset behavior.

To my mind it depends on the likelihood of something having changed and 
whether that change might affect what you would be doing with the action that 
follows. For example. if you're trying to fix the execution of a particular 
task, you would expect to see any change in the recipe / configuration to take 
effect when re-running the task.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre