Bug 7683

Summary: Provide means of turning a recipe change into a bbappend
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Paul Eggleton <bluelightning>
Component: devtools / tool chainAssignee: Unassigned <unassigned>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: Medium+ CC: akuster, alexandru.c.georgescu, jose.perez.carranza, meta.mr.watcher, meta.watcher, pavel, randy.macleod, sgw
Version: 1.8   
Target Milestone: 5.99   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description Paul Eggleton 2015-04-30 15:56:42 UTC 
For the purposes of having changes to a recipe in a form which can be maintained, it might be useful to be able to turn a commit making direct edits to a recipe into a bbappend on top of the original recipe. We can simply compare a parse of the recipe before and after the change and set values in the bbappend accordingly; then we'd just need to pick up any added/changed files alongside the recipe.
Comment 1 Armin Kuster 2019-12-22 21:25:28 UTC 
what does this mean in the current context of using overides?
Comment 2 Paul Eggleton 2019-12-22 22:29:44 UTC 
Overrides would have to be taken into account, I agree, but that's not really a new thing.
Comment 3 Randy MacLeod 2023-10-24 14:24:24 UTC 
Bulk move from 4.99 or 0.00 to 5.99
Comment 4 Randy MacLeod 2025-02-14 16:46:33 UTC 
bulk change to add Saul's non-WR address.
Comment 5 Randy MacLeod 2025-02-14 16:48:09 UTC 
Bulk change: Remove Saul's old WR address.