[OE-core] [PATCH 1/1] rm_work.bbclass: inhibit rm_work per recipe

[Phil Blundell]

On Tue, 2013-03-26 at 17:12 +0000, Paul Eggleton wrote:
> On Wednesday 13 March 2013 15:01:33 Qi.Chen at windriver.com wrote:
> > From: Chen Qi <Qi.Chen at windriver.com>
> > 
> > Use RM_WORK_WHITELIST to inhibit rm_work per recipe. In this way,
> > one can use rm_work for the most of the recipes but still keep the
> > work area for the recipe(s) one is working on.
> > 
> > As an example, the following settings in local.conf will inhibit
> > rm_work for icu-native, icu and busybox.
> >     INHERIT += "rm_work"
> >     RM_WORK_WHITELIST += "icu-native icu busybox"
> > 
> > If we comment out the RM_WORK_WHITELIST line and do a rebuild, the
> > working area of these recipes will be cleaned up.
> 
> This is a great feature, but I just looked at it and realised that the term 
> "whitelist" isn't really correct - this is more of a blacklist.

This doesn't seem (at the risk of invoking an unintended metaphor)
entirely black or white.  Maybe it should just be "RM_WORK_EXCEPTIONS"
or something.

Of course, you can get the same effect in your distro configuration by
saying:

RM_WORK = "rm_work"
RM_WORK_pn-icu-native = ""
INHERIT += "${RM_WORK}"

so I must admit to being slightly ambivalent about whether the extra
syntactic sugar is all that valuable.  And then again you can always use
rm_old_work instead. :-)

p.