3675 2013-01-04 10:52:37 +0000 inhibit rm_work per recipe 2013-03-19 14:49:40 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core unspecified x86 Multiple VERIFIED FIXED Low enhancement 1.4 1 fransmeulenbroeks Qi.Chen liezhi.yang meta.mr.watcher meta.watcher poky.bs.watcher poky.watcher Qi.Chen sgw sstncr yi.zhao --- Unknown (Hard to categorize) --- oldest_to_newest 28550 0 fransmeulenbroeks 2013-01-04 10:52:37 +0000 28551 1 fransmeulenbroeks 2013-01-04 10:57:33 +0000 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 30640 2 Qi.Chen 2013-03-12 08:50:35 +0000 I think this feature might be useful. And at the first thought, using a white list seems simpler. 30826 3 Qi.Chen 2013-03-19 07:20:32 +0000 merged into poky/master: 83409910dd3a31589ca9ea4172a70f0bcd877d8f http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=6c930c3c06f2e698540626c87bd7f7f571df35ef 30852 4 sstncr 2013-03-19 14:49:40 +0000 Verified / commit 410d1e049a1933c44b29416f3ac833ed001f8248