Bug 11434

Summary: devtool edit-recipe/find-recipe enhancements
Product: [Build System, Metadata & Runtime] OE-Core Reporter: brian avery <brian.avery>
Component: Scripts and ToolsAssignee: Rebecca Chang <rebecca.swee.fun.chang>
Status: VERIFIED FIXED QA Contact: Ashwin Soman <ashwinx.soman>
Severity: enhancement    
Priority: Medium+ CC: ashwinx.soman, bluelightning, ee.peng.yeoh, ross.burton
Version: 2.4   
Target Milestone: 2.4 M2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description brian avery 2017-05-01 22:02:44 UTC 
right now devtool edit-recipe has ugly tracebacks if executed w/o an EDITOR available. This happens in the build containers. It would be nice to 
1) say  : no EDITOR defined/available. exiting politely....
2) provide a devtool find-recipe which prints out the path to the recipe.
Comment 1 Rebecca Chang 2017-07-13 05:20:30 UTC 
I have pushed the patch to mailing list for review.
http://lists.openembedded.org/pipermail/openembedded-core/2017-June/138842.html
Comment 3 Ashwin Soman 2017-10-02 07:07:12 UTC 
Changes have been verified.
devtool find-recipe  was added and in case of no editor available devtoot edit-recipe simply returned   
/bin/sh: 1: vi: not found
ERROR: Execution of 'vi' failed:
Comment 4 Ashwin Soman 2017-10-03 05:33:24 UTC 
IT seems like edit-recipe and find-recipe functionality is already being tested in oeselftest.
Does your enhancement require any other automated test other than the existing once.
Comment 5 Rebecca Chang 2017-10-03 05:45:43 UTC 
(In reply to comment #4)
> IT seems like edit-recipe and find-recipe functionality is already being
> tested in oeselftest.
> Does your enhancement require any other automated test other than the
> existing once.

No, existing one should be sufficient to cover the scope of this issue.
Thanks.
Comment 6 Ashwin Soman 2017-11-08 05:25:14 UTC 
Bug have been resolved and verified