Bug 7683 - Provide means of turning a recipe change into a bbappend
Summary: Provide means of turning a recipe change into a bbappend
Status: NEW
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 1.8
Hardware: All Multiple
: Medium+ enhancement
Target Milestone: 5.99
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-04-30 15:56 UTC by Paul Eggleton
Modified: 2025-02-14 16:48 UTC (History)
8 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.