Bug 7637

Summary:	devtool: add: interactive recipe creation
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Paul Eggleton <bluelightning>
Component:	devtools / tool chain	Assignee:	David Reyna <david.reyna>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	meta.mr.watcher, meta.watcher, randy.macleod, sgw
Version:	1.8
Target Milestone:	Future
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-21 13:44:31 UTC

At the moment, devtool add (actually recipetool create since devtool add wraps around that) only examines the source code when creating a recipe for a source tree, and does so non-interactively, expecting the user to fix up the recipe afterwards. We could improve the utility of this function significantly by creating an interactive process which does the following:

1) Guide the user through filling in any missing information for the recipe (license, dependencies, configure arguments, do_configure/do_compile/do_install for makefile-based software, etc.)

2) Offer the ability to enable additional functionality, e.g. classes such as useradd, update-rc.d, systemd, etc.

This should be implemented in such a way that we can offer this through the Eclipse plugin as well as on the command-line - i.e. there needs to be an API abstraction for actually presenting the UI.

Comment 1 Paul Eggleton 2015-07-10 11:01:26 UTC

Just to be clear, this bug covers only the backend / console level implementation of this functionality, not also the Eclipse integration - but we need to consider how Eclipse might be able to call into the code in order to provide a front end to the process.