> The bitbake-layers command is needed only to generate the layer config file
> (in json format) out of an already existing yocto setup. It does not perform
> the actual layer fetch/setup from the json. That's the feature I like the most
> in my proposal: none of the other tools bootstrap the confi
On Wed, 3 Aug 2022 at 23:02, Chris Laplante via lists.openembedded.org
wrote:
> But IMHO bundling the layer setup tool inside bitbake itself feels a bit like
> the chicken-and-egg problem. I'd like my spec file (or JSON file, kas
> configuration file, whatever) to be a complete manifest of thing
Hi Alex,
> do you think any of these pieces could be moved to 'official yocto',
> specifically as bitbake-layers subcommands? I read through the README, and
> it seems that things like 'status' and 'run' would fit very well there.
I would agree that 'status' and 'run' would be useful additions, t
Hello Chris,
do you think any of these pieces could be moved to 'official yocto',
specifically as bitbake-layers subcommands? I read through the README,
and it seems that things like 'status' and 'run' would fit very well
there.
Also note that there's a proposal for a json schema and layer toolin
Hi all,
Today I'm excited to publish a tool I've been developing internally for about a
year now. It is called 'yb', and you can think of it like a cross between kas,
Google's repo, and myrepos (mr).
Project page: https://github.com/Agilent/yb
Download it here: https://github.com/Agilent/yb/rel
