Bug 3675 - inhibit rm_work per recipe
Summary: inhibit rm_work per recipe
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Low enhancement
Target Milestone: 1.4
Assignee: Chen Qi
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-01-04 10:52 UTC by Frans Meulenbroeks
Modified: 2013-03-19 14:49 UTC (History)
9 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Unknown (Hard to categorize)
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frans Meulenbroeks 2013-01-04 10:52:37 UTC

    
Comment 1 Frans Meulenbroeks 2013-01-04 10:57:33 UTC
Sorry, has some problem witth the gui and hit submit prematurely.

Here is the description

It would be convenient if, when using rm_work one could specify in e.g. local.conf for which recipes this should not apply.
That way one can use rm_work for most of the recipes but keep the work area for the recipe(s) one is working on.

A way to achieve that could be to say in e.g. local.conf:
NO_RM_WORK_squashfs-tools = "1"
or something like that.

Of course another way to whitelist recipes for which rm_work is not desired is also fine.

On a related note: probably rm_work should also not function if a user has made manual changes in the work area (e.g. when running a devshell
Comment 2 Chen Qi 2013-03-12 08:50:35 UTC
I think this feature might be useful.
And at the first thought, using a white list seems simpler.
Comment 3 Chen Qi 2013-03-19 07:20:32 UTC
merged into poky/master: 83409910dd3a31589ca9ea4172a70f0bcd877d8f

http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=6c930c3c06f2e698540626c87bd7f7f571df35ef
Comment 4 Stefan Stanacar 2013-03-19 14:49:40 UTC
Verified / commit 410d1e049a1933c44b29416f3ac833ed001f8248