summaryrefslogtreecommitdiffstats
path: root/recipes-containers/docker-compose/files/0001-setup.py-import-fastentrypoints.patch
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@gmail.com>2023-11-07 00:34:18 +0000
committerBruce Ashfield <bruce.ashfield@gmail.com>2023-11-07 13:22:17 +0000
commit92a7e8ec4639be5c0d6988353c649949d7e17f83 (patch)
tree2226dbac9d31fb5032593568a779b224f2030b1b /recipes-containers/docker-compose/files/0001-setup.py-import-fastentrypoints.patch
parentf7bffb351c59cc972d9141ac2ab5ee2c40e19547 (diff)
downloadmeta-virtualization-92a7e8ec4639be5c0d6988353c649949d7e17f83.tar.gz
kernel: allow configuration to be skipped .. but warn
Allow the kernel include file to be skipped, even if a kernel is capable of merging and using the fragments in the layer and kernel-cache. Setting SKIP_META_VIRT_KERNEL_INCLUDE="t" in a kernel bbappend, or in a configuration file will inhibit the generated / detected include file. BUT If that opt-out is done, we warn, as the user has explicitly disabled safeguards that help ensure that subtle runtime issues aren't introduced. BUT If someone really knows what they are doing, they don't want the warning to be present in each build. So setting META_VIRT_KERNEL_CHECK_WARNING_INHIBIT="t" will inhibit the message. At that point, you have jumped through all the hoops and you are free to ensure your kernel configuration is correct using other means. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Diffstat (limited to 'recipes-containers/docker-compose/files/0001-setup.py-import-fastentrypoints.patch')
0 files changed, 0 insertions, 0 deletions