Greetings, I was curious where the Yocto binary distro work ended up? I was looking at Michael's email thread and talk.
https://lists.openembedded.org/g/openembedded-architecture/topic/102755562#msg1846 https://rootcommit.com/pub/conferences/2024/elce/yocto-binary-distro/yocto-binary-distro.pdf (https://www.youtube.com/watch?v=UdJZ0xz-QLk) I've looked through parts of the wiki (e.g.https://wiki.yoctoproject.org/wiki/Binary_Distro_Process ). Does my understanding as follows sound correct? Yocto doesn't provide a binary distro, so we first build with Yocto from source, e.g., a small generic x86 kernel and then setup a feed of kernel module pkgs and pkg world. Can I assume a user's only option to build a system, would be to boot a system to use the feed "online" to make a rootfs have everything they need? Or are there more options for composing offline so the end users grabs a kernel and a script that pulls a rootfs together offline from emulation/hw/yocto env?(debootstrap like) Thank you for any insight on this so we can find the right starting point and list of open issues (if that exists)! Regards, Matt
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2216): https://lists.openembedded.org/g/openembedded-architecture/message/2216 Mute This Topic: https://lists.openembedded.org/mt/117514584/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
