meta-raspberrypi VS yoe-distro

How do you figure Pis have bad integration with Yocto?

https://github.com/agherzan/meta-raspberrypi

For what it's worth, the entire Pi lineup is also well supported by Buildroot. In-tree, no less.

Embedded linux exactly. Major OEMs are using yocto. Check https://www.yoctoproject.org/

Been there. You don't want alpine or debian. Good gpos, but what you want is Yocto, which will let you build exactly and only what you need piece by piece including only the kernel modules for your hardware, the exact applications you use and no extras, and with a little extra tweaking, you can wire in Mender for ota updates and the ability to push custom images to clients that need specialization, or even fully unlocked images for customers that need it, plus if you're using an SD card, you can send users recovery drives instead of shipping full devices or let them build their own images without your proprietary code

I second Yocto. It's the kernel in use by the OpenBMC project

One last "option" is yocto but tis is not good for desktop, but it can be a fun project.

Thanks, u/baudvine, that should be the common way to go. While skimming through several Github repos - where mainly this solution is used or some type of submodule mechanics like here - I am really wondering how I could miss that. Anyway, thanks for pointing me in the right direction!

Raspian is from Debian which is a binary distro and Debian is for Server/Desktop systems. Yocto Project/ObenEmbedded are binary distros where you need to build everything from sources and made for constrained embedded systems. So you rather add whatever you need than start for a huge image. You can ask on https://github.com/agherzan/meta-raspberrypi for a bigger image. Also you might want to look at https://github.com/YoeDistro/yoe-distro But I don't see a huge image there as well.