diff options
| author | Bruce Ashfield <bruce.ashfield@gmail.com> | 2026-03-12 17:50:02 +0000 |
|---|---|---|
| committer | Bruce Ashfield <bruce.ashfield@gmail.com> | 2026-03-12 19:06:40 +0000 |
| commit | c2eeba33360b0941ff2a89f44712e9212066f786 (patch) | |
| tree | 61f438c4e77a46de8cc5d4651b8fb3958985b69f /recipes-devtools/python/python-gevent | |
| parent | d16110ae98c36572dbf39af487f426f60842313e (diff) | |
| download | meta-virtualization-c2eeba33360b0941ff2a89f44712e9212066f786.tar.gz | |
kernel: skip kcfg search path injection for kernels with kernel-cache
The kcfg sysroot search path (type=kmeta) was being injected
unconditionally, which caused fragment conflicts for linux-yocto kernels
that already have their own kernel-cache meta branch. The injected
search path would roll back fragments to an older set.
Make the injection conditional and fix the root cause:
- kernel_cache_feature() now checks SRC_URI for type=kmeta entries.
Kernels with kernel-cache get short paths (e.g. cfg/container.scc)
that resolve directly via the kernel-cache's search path. Kernels
without kernel-cache get the sysroot-relative ../../ paths as before.
- distro_cond_feature() now passes d.getVar('SRC_URI') instead of an
empty string, so kernel_cache_feature() can actually see whether the
kernel has a kernel-cache.
- SRC_URI append and inject_kcfg_search_path prefunc skip when
type=kmeta is already present.
- Remove unused kernel_cache_cond_feature() which was the original
conditional implementation but was never wired up.
This restores the original design intent from commit 5c212911
("allow conditional use of yocto-cfg-fragments"): kernel-cache is
the first choice for fragment resolution, sysroot is the fallback.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Diffstat (limited to 'recipes-devtools/python/python-gevent')
0 files changed, 0 insertions, 0 deletions
