| Summary: | [HOB] Add a recipe feature | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Hob | Reporter: | Dave Stewart <david.c.stewart> |
| Component: | hob | Assignee: | Belen Barros Pena <belen.barros.pena> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | bluelightning, jessica.zhang, poky.bs.watcher, poky.watcher, richard.purdie |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | Other | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Dave Stewart
2012-08-10 16:19:35 UTC
We need to revisit all the tools we have and have a clear definition of their charters and make improvement accordingly or see how to improve their interaction. Currently recipe wizard is in Eclipse and our definition is Eclipse is a dev tool where Hob is a build tool. Would like to respectfully disagree with the "low" priority and suggest that it is high or medium plus. davest's thinking follows... We were sitting with some engineers who are new to Yocto and talking about their experiences with the system. The complaint about Hob was that it's nice for an initial build experience, but it lacks the ability to access a broad selection of packages like a regular distro. Yeah, usually these are in meta-oe or you might need to craft a simple new recipe. Yes, the wizard for this belongs in the Eclipse tools. We need to extend the usefulness of Hob, however, to increase the adoption of Yocto. I'm afraid that if we require someone to install Eclipse just to develop a simple new recipe, it will stop people from playing with the system. I was hoping we could re-use the logic from the Eclipse tools here. Of course, I am open to discussion on this. :-) Sorry for the strange spelling of the bug report - I was typing it on my smart phone and spell correction was killing me. I am wondering if the Web Hob project has changed our views on adding this functionality to the GTK Hob. My inclination is to keep GTK Hob as simple as possible (an assistant for simple image building), and leave more sophisticated capabilities like searching for and adding existing oe-core recipes, or create your own recipe assistants, for the web-based tool. A simple way to somehow facilitate recipe adding in GTK Hob could be providing a link to the new oe-core layer index Paul E is working on (when it becomes available). In this layer index, I will be able to search all recipes, layers and machines in oe-core. I can then download layers (or recipes) and incorporate them into GTK Hob via a layer. We could then document the workflow as part of the Hob manual, and make sure we link to the information within Hob. This should be put into consideration to be incorporated into webhob features |