Bug 15824

Summary: rm_work and populate_sdk
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Sean Nyekjaer <sean>
Component: coreAssignee: Unassigned <unassigned>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Medium CC: antonin.godard, meta.mr.watcher, meta.watcher, randy.macleod, yoann.congal, zhangle.yang
Version: unspecified   
Target Milestone: 6.1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Sean Nyekjaer 2025-04-08 06:19:41 UTC 
When rm_work is enabled and when building an image it works as I would
expect.
But when running populate_sdk for that image, it doesn't look like it's
running the rm_work task and the disk usage increases.

I have tried adding [0] to my image recipe, and it makes a significant
difference in disk usage.

Some numbers for reference::
With sstate and without [0]:
26G     build/
With sstate and with [0]:
18G     build/
Without sstate and without [0]:
120G    build/
Without sstate and with [0]:
29G     build/
Comment 1 Antonin Godard 2025-04-10 14:19:36 UTC 
[0] was forgotten to be included:

  addtask do_populate_sdk_and_rmwork after do_populate_sdk
  do_populate_sdk_and_rmwork[recrdeptask] = "do_rm_work"

From https://lists.openembedded.org/g/openembedded-core/message/214401.
Comment 2 Randy MacLeod 2026-04-15 19:15:02 UTC 
This looks like a nice simple bug fix / enhancement for 6.1.