| Summary: | clean up hob and bitbake interaction via well-defined APIs/abstractions | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Hob | Reporter: | Jessica <jessica.zhang> |
| Component: | hob | Assignee: | Bogdan Marinescu <bogdan.a.marinescu> |
| Status: | VERIFIED NOTABUG | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | bogdan.a.marinescu, cristian.iorga, mihai.lindner, poky.bs.watcher, poky.watcher, valentin.popa |
| Version: | unspecified | ||
| Target Milestone: | 1.4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 3211 | ||
|
Description
Jessica
2012-12-12 18:35:36 UTC
This bug needs more information. What part of the hob/bitbake interaction needs to be clarified/improved? Switching to "NEEDINFO" (see my previous question). Bogdan, THis will be covered in our overall design for bitbake to better support client/server architecture. We need a well designed (if in place) and documented abstract API layer for client to interact with bitbake server. As discussed with Jessica and Richard, the current API is most likely generic enough for what we're trying to achieve. Its documentation should be improved, but that's the subject for another bug, so I'm closing this one. Not a bug. |