| Summary: |
Change image recipes to include package-management IMAGE_FEATURES explicitly |
| Product: |
[Build System, Metadata & Runtime] OE-Core
|
Reporter: |
Scott Garman <scott.a.garman> |
| Component: |
core | Assignee: |
Paul Eggleton <bluelightning> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium
|
CC: |
meta.mr.watcher, meta.watcher
|
| Version: |
unspecified | |
|
| Target Milestone: |
1.3 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
---
|
|---|
Our image recipes do not make it clear when package-management is one of the IMAGE_FEATURES. For example, core-image-minimal does not include package-management. However, core-image-sato does, since it is included as part of ${X11_IMAGE_FEATURES}. It does not make sense to couple package-management with X11 image features. To improve our readability and usability to new image recipe writers, package-management should be mentioned explicitly in IMAGE_FEATURES for the images which use it.