| Summary: | Add an easy to use script like AUH (auto upgrade help) | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Robert Yang <liezhi.yang> |
| Component: | Scripts and Tools | Assignee: | Robert Yang <liezhi.yang> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Undecided | CC: | bluelightning, richard.purdie, ross.burton |
| Version: | 2.1 | ||
| Target Milestone: | 2.1 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Robert Yang
2015-12-04 03:02:43 UTC
FYI 1 & 2 can be done by "devtool upgrade" right now. Also the AUH is designed to be able to be run standalone, although it's not the primary use case. I'm a little bit concerned about duplication here. As Paul mentions, devtool upgrade already covers some of this for 1 and 2. For 3, I'm worried that testing each PACKAGECONFIG would cause problems when you consider something large like mesa so that may not be feasible. For 4, Martin has done some similar work but wouldn't we want to enhance the AUH code to handle this? I'd also like to understand why we need a new script when we have AUH and devtool. What is the usecase for something in addition to just enhancing those? I'd also note that my hope is that in future there will be more sharing of code between the AUH and "devtool upgrade" so that even that effective duplication goes away. Sorry, I don't know much about AUH, if AUH can do some similar work, then I will close this one. |