that's deployment. yocto only has half baked support for a binary layers, let alone binary sdk layers, where you add more packages, for the target or the buil

that's deployment. yocto only has half baked support for a binary layers, let alone binary sdk layers, where you add more packages, for the target or the build host, and more layers come further down. this is for you to use the binary packages to build your images. which you then deploy, as you suggest. key thing: you use suse/ubuntu/redhat binary packages to build and create your add-ons which you then deploy, as image-on-the-fly (created on target during traditional Linux install/update), or as precooked image (qemu, container or, new: embedded flash image)