Binary Artifacts and the Ease of Use Onramp for the Yocto Project
summary
Yocto builds produce reusable binary feeds—RPM/IPK/DEB packages, DTBs, kernels, SDKs and OCI images—that can be served over HTTP and consumed by a running target to add packages to a running image without reflashing. The demo uses bitbake, package-index, a Python web server, DNF, and shows PR service and sstate hash-equivalence creating upgraded package revisions; installing Moby/Docker pulls ~236 packages and grows kernels from 4 to 33. The build also emits a container base OCI image that is pushed, pulled and run on target.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:20Binary Artifacts Ease of Use
- 10:27Example Binary Artifacts
- 12:18Build Configuration
- 13:25Shared State
- 13:45Package Revision Service
- 20:12Reproducibility
- 21:31How Can You Extend a Platform
- 37:57Container Base and Meta Virtualization
- 40:29Binary Artifacts Working Group
related talks
30mYocto for open source embedded systems development
36mEmbedded Development Made Easy: A Guide to FOSS Platforms and Maxing product value
45mOverlay Images To the Rescue
42mHey Yocto, Build Me a Custom Embedded Linux! Er, No
39mBoF: The Yocto Project and OpenEmbedded
01h 02mBoF: The Yocto Project and OpenEmbedded
11mBeth Flanagan (Intel) Interview - OSCON 2014
31mA Million Ways to Provision Embedded Linux Images