| Summary: | devtool documentation needs to mention oe-local-files | ||
|---|---|---|---|
| Product: | [Documentation] General Docs | Reporter: | Paul Eggleton <bluelightning> |
| Component: | docs-general | Assignee: | Michael Opdenacker <michael.opdenacker> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | mark.morton, michael.opdenacker, randy.macleod, srifenbark, tim.orling |
| Version: | unspecified | ||
| Target Milestone: | 3.4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | 24 June 2018: IN PROGRESS DESIGN | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Paul Eggleton
2018-12-12 19:23:08 UTC
Paul, What happens to the "oe-local-files" folder that is created under any newly created source tree after the user runs "devtool finish"? Running "devtool finish" copies any modified non *.patch and *.diff files back up into the source tree where they originated presumably overwriting the originals so the changes are preserved. Is that "oe-local-files" folder deleted or does it hang around? Another question... For "devtool modify", three common entry points are documented for starting the tool (see https://yoctoproject.org/docs/2.7/sdk-manual/sdk-manual.html#sdk-devtool-use-devtool-modify-to-modify-the-source-of-an-existing-component). For the "left" scenario, is the "oe-local-files" folder a sub folder of "sources"? For the right scenario, we don't create a "oe-local-files" folder in the 3rd-party extracted source tree do we? Can you give me more details for the left and right entry scenarios? Thanks, Scott Paul, Please answer this question. The oe-local-files subdirectory is preserved after devtool finish, just like the rest of the source tree. Note that oe-local-files wouldn't contain any .patch/.diff files (if that's what you meant) since those are handled in the form of commits in git within the source tree. Re the other branches, the middle branch is pretty much the same as the left - we're just telling it to put the source tree in a specific location rather than using the default under the workspace. For the right hand branch, files in an oe-local-files subdirectory will be used if the subdirectory exists, however if it does not by the time that you run devtool finish then the files will be removed from next to the recipe (and SRC_URI) because it will appear to devtool as if you deleted them. Paul, Can you review the changes to the first section based on your comments? https://yoctoproject.org/docs/2.8/sdk-manual/sdk-manual.html#sdk-devtool-use-devtool-modify-to-modify-the-source-of-an-existing-component Thanks, Scott Paul, Here is the final. If you could read it over and let me know if we are good I can close this bug. Thanks, Scott https://yoctoproject.org/docs/2.8/sdk-manual/sdk-manual.html#sdk-devtool-use-devtool-modify-to-modify-the-source-of-an-existing-component https://yoctoproject.org/docs/2.8/sdk-manual/sdk-manual.html#sdk-devtool-use-devtool-upgrade-to-create-a-version-of-the-recipe-that-supports-a-newer-version-of-the-software Pinging for review. Thanks, Scott Paul, Can you look at the following: https://yoctoproject.org/docs/3.0/sdk-manual/sdk-manual.html#sdk-devtool-use-devtool-modify-to-modify-the-source-of-an-existing-component https://yoctoproject.org/docs/3.0/sdk-manual/sdk-manual.html#sdk-devtool-use-devtool-upgrade-to-create-a-version-of-the-recipe-that-supports-a-newer-version-of-the-software Thanks, Scott Closing this bug as it seems that Scott properly included this topic in the documentation. |