Bug 8594 - devtool: provide easy means of moving a recipe in the workspace to a real layer
Summary: devtool: provide easy means of moving a recipe in the workspace to a real layer
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: 2.0
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 2.2
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-10-28 09:12 UTC by Paul Eggleton
Modified: 2016-07-20 13:41 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2015-10-28 09:12:24 UTC
At the moment, if you do a "devtool add" or a "devtool upgrade", you need to take care of moving the created recipe to a real layer manually; it would be nice to provide a single command (or option to update-recipe) that would do that for you. 

The tricky thing is when you do "devtool update-recipe" in this situation, your changes are only going into the workspace, whereas when you do it after doing "devtool modify" your changes go back to the "real" recipe that's already in a proper layer; this may be a little confusing if you don't know what's going on behind the scenes. If practical it would be nice to smooth this out; does it make sense to have a two-step process where you use "devtool update-recipe" to update the recipe in the workspace and then another command to copy/move that recipe and associated files to a real layer?
Comment 1 Ross Burton 2016-07-20 13:41:57 UTC
Fixed in oe-core fa550fcb9333d59b28fc0e4aebde888831410f5c.