We really are big fans of KAS. I'm giving a talk on it tomorrow at the Yocto Summit https://summit.yoctoproject.org/yocto-project-summit-2022-11/talk/BZNRTF/
We can help you with the setup, but it REALLY shines in CI. We use it for Gitlab CI, and I would highly recommend you do something similar. See https://gitlab.com/jonmason00/meta-arm/-/pipelines for a publicly visible version of the CI we do for meta-arm.
Thanks, Jon
-----Original Message----- From: Ross Burton Ross.Burton@arm.com Sent: Tuesday, November 29, 2022 8:59 AM To: Pawel Zalewski pzalewski@thegoodpenguin.co.uk Cc: Vincenzo Frascino Vincenzo.Frascino@arm.com; Alex J Lennon ajlennon@dynamicdevices.co.uk; Andrew Murray amurray@thegoodpenguin.co.uk; Manjunatha Mulki Bhat manjubhat@gmail.com; Steve Capper Steve.Capper@arm.com; Jon Mason Jon.Mason@arm.com; linux-morello-distros@op-lists.linaro.org Subject: Re: [linux-morello-distros] Yocto on Morello Round Table
On 29 Nov 2022, at 11:34, Pawel Zalewski pzalewski@thegoodpenguin.co.uk wrote:
Hi Vincenzo,
The manifest is there to fetch the meta-arm layer as meta-morello appends recipes found in the meta-arm's bsp, the manifest will also fetch Yocto kirkstone and meta-morello itself. So at the end the developer will end up with a checkout of kirkstone with meta-arm and meta-morello placed inside its poky tree.
FWIW, in meta-arm we’re big fans of Kas (https://kas.readthedocs.io/). It integrates with Yocto so does more than just fetching, and doesn’t involve another repository just for the manifest.
Ross