Re: [PATCH] rm_work.bbclass: allow a shell var to override rm_work

[Andreas Oberritter <obi@opendreambox.org>]

On 12/12/2010 04:03 PM, Frans Meulenbroeks wrote:
> Sometimes one is building with rm_work, but for a specific build you want to
> keep the work even if the build is successful.
> One way to achieve this is to comment the INHERIT += "rm_work" from your
> local.conf file, but this means that all recipes need to be reparsed which takes some time.
> 
> This patch introduces a variable KEEP_WORK
> If this variable is set the work will not be removed.
> Intended use is
> KEEP_WORK=1 bitbake yourrecipe.bb
> Default behaviour is kept the same (in case KEEP_WORK is not set)
> 
> Note that in order for this to work KEEP_WORK needs to be added to the env var BB_ENV_EXTRAWHITE
> e.g. export BB_ENV_EXTRAWHITE="KEEP_WORK"
> 
> We still might want to improve the test so it only keeps the work if KEEP_WORK is > 0
> (or do not execute the task at all if KEEP_WORK is not set).
> Also we might want to add KEEP_WORK to the whitelist of vars that are always ok
> 
> Signed-off-by: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>

I'd prefer a variable with a prefix like OE_, but that's probably just a
matter of taste. Are there any guidelines?

This patch motivates me to enable rm_work by default for our distro. It
would be nice if this variable would become documented on the wiki.

Acked-by: Andreas Oberritter <obi@opendreambox.org>