On Wed, 22 Nov 2023 at 21:04, Michael Opdenacker via lists.openembedded.org <[email protected]> wrote: > - Beginner use case: begin by fetching a binary image, ready to boot on a > target machine. Extend the system by installing extra applications > through > package feeds. > > - Intermediate use case: tweak and rebuild existing packages, compile new > applications and modify images by using an eSDK and other binary > artifacts. > > - Advanced use case: completely reorganize and optimize the system for a > specific target, switching to building from source
I would actually suggest that the esdk is skipped altogether: it provides a restricted, locked down environment without access to bitbake or possibility to modify the build. It's not a 'real yocto'. Rather, let's give the users the possibility to go directly to the full yocto build that was used to produce the binary images. To that end, I've proposed a prototype for making 'build bundles': https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/ It would need a corresponding user-facing piece, e.g. oe-setup that would take and unpack and setup the bundle from the server, ensuring it does match the binary image. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1850): https://lists.openembedded.org/g/openembedded-architecture/message/1850 Mute This Topic: https://lists.openembedded.org/mt/102755562/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
