| Summary: | COMPATIBLE_MACHINE or COMPATIBLE_HOST but against LAYERSERIES_CORENAMES | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | jonathan.yong |
| Component: | core | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Undecided | CC: | meta.mr.watcher, meta.watcher, richard.purdie |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
jonathan.yong
2020-09-24 01:32:23 UTC
I can see why this would seem like an attractive idea. Unfortunately this is not a behaviour we want to encourage though. We need to make it clear which versions of core are compatible with which layers. If we supported something like this, it would imply that may different branches could all be intermixed and expected to work and we'd end up in a mess. Its a sad fact that users already struggle with layer quality, intermixing things that work out as untested and incompatible. Also consider that newer versions deprecate and remove functionality (like file:// url globbing) or will rename variables for the inclusive language changes we have that are coming up. As such whilst technically possible, we probably should go in this direction. |