On Thu, 7 May 2026 at 15:20, Richard Purdie <[email protected]> wrote: > The trouble is there are multiple things a user may want to do and > which one is a hard choice to make. If you have some narrow layer with > a specific image and application, that is easy. If you have a general > layer like meta-virtualization, it is unclear which target(s) a given > user may want. nodistro/poky face the same challenge, the thing the > user might want "depends".
For such general layers two things come to mind: 1. An example/demo/starting point for one or a handful of most common use cases. E.g. poky/nodistro would showcase two or three most common core- images. 2. Running tests for locally made changes, before submitting a patch. For oe-core/poky that's perhaps unrealistic, but I can imagine something domain-specific like meta-virtualization could define steps for this: $ bitbake-setup run test Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2335): https://lists.openembedded.org/g/openembedded-architecture/message/2335 Mute This Topic: https://lists.openembedded.org/mt/119195970/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
