| Summary: | wic: bootimg_dir lost to source plugins when auto detecting | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ola Nilsson <ola.x.nilsson> |
| Component: | deployment | Assignee: | Tom Zanussi <tom.zanussi> |
| Status: | RESOLVED OBSOLETE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | ola.x.nilsson |
| Version: | unspecified | ||
| Target Milestone: | 1.8 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Ola Nilsson
2014-09-10 15:04:39 UTC
I believe the following patch changes things so that this should no longer be a concern. Basically bootimg_dir now only refers to the bootimg_dir defined on the command line, if specified, otherwise plugins are responsible for finding the bootimg_dir they need otherwise e.g HDDDIR or whatever. commit 42d0334aa8bf59937262f957f2ea04abc271138b Author: Tom Zanussi <tom.zanussi@linux.intel.com> Date: Wed Oct 29 17:04:23 2014 -0500 wic: Remove special-case bootimg_dir The first iterations of wic very shortsightedly catered to two specific use-cases and added special-purpose params for those cases so that they could be directly given their corresponding boot artifacts. (hdddir and staging_data_dir). As more use-cases are added, it becomes rather obvious that such a scheme doens't scale, and additionally causes confusion for plugin writers. This removes those special cases and states explicitly in the help text that plugins are responsible for locating their own boot artifacts. |