| Summary: | inhibit rm_work per recipe | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Frans Meulenbroeks <fransmeulenbroeks> |
| Component: | core | Assignee: | Chen Qi <Qi.Chen> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | liezhi.yang, meta.mr.watcher, meta.watcher, poky.bs.watcher, poky.watcher, Qi.Chen, sgw, sstncr, yi.zhao |
| Version: | unspecified | ||
| Target Milestone: | 1.4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | Unknown (Hard to categorize) |
| Verified: | Documentation change: | --- | |
|
Description
Frans Meulenbroeks
2013-01-04 10:52:37 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 I think this feature might be useful. And at the first thought, using a white list seems simpler. merged into poky/master: 83409910dd3a31589ca9ea4172a70f0bcd877d8f http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=6c930c3c06f2e698540626c87bd7f7f571df35ef Verified / commit 410d1e049a1933c44b29416f3ac833ed001f8248 |