On 02.09.2019 15:51, Josef Holzmayr wrote: > I'd like to throw kas into the discussion too, I've been using it quite > successfully. > > https://github.com/siemens/kas +1 for kas. Previously I was using repo, custom scripts and custom Docker container for running the build. kas does all of that and makes significantly faster for me to start a new project.
I have described my repo vs kas experience a while ago if someone would be interested: https://blog.3mdeb.com/2019/2019-02-07-kas/ I hope it's fine to link to one's blog post there? > > Greetz > > On Mon, Sep 02, 2019 at 03:34:28PM +0200, Alexander Kanavin wrote: >> On Mon, 2 Sep 2019 at 15:05, Brian Silverman <b...@readysetstem.com> wrote: >> >>> The tags chosen above are based on what we test and ship. So my issue is >>> that someone has to correctly follow the above instructions for different >>> versions of multiple layers if they want a reproducible build of a specific >>> version of mylayer-image. >>> >>> Is there a canonical why to encode this information within my layer? >>> Obviously I could script the above, store it in my layer, and have the user >>> run that script. But, that seems very unyocto-like. >>> >> At the moment Yocto project does not have an off-the shelf setup for >> multiple layers. You are welcome to provide and maintain one, until then it >> is indeed custom scripts, or tools like Google's 'repo', or maybe git >> submodules could work. >> >> Alex >> -- >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > -- Maciej Pijanowski Embedded Systems Engineer https://3mdeb.com | @3mdeb_com
signature.asc
Description: OpenPGP digital signature
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
