On 7/10/2018 1:04 PM, Michael Habibi wrote:
Well I should have just used what I want to actually do as the
example, and not a QA action.
I want to create a new type of manifest that is only my layer, that
will include line items that basically has like: package name,
version, download URL,
Well I should have just used what I want to actually do as the example, and
not a QA action.
I want to create a new type of manifest that is only my layer, that will
include line items that basically has like: package name, version, download
URL, checksum, license.
I have no idea yet how to
Hypothetically a new QA action should be added at the distro level, by
writing a class and adding it to INHERIT.
(I've several new QA tests added in this way)
Ross
On 10 July 2018 at 19:53, Alexander Kanavin wrote:
> Yes. Implement a class and inherit it from the recipes.
>
> Alex
>
>
Yes. Implement a class and inherit it from the recipes.
Alex
2018-07-10 20:50 GMT+02:00 Michael Habibi :
> I was wondering if there is a way I can apply a global modification to all
> recipes in a layer? For instance, we have our own layer for our changes that
> sit on top of the base Yocto/OE
I was wondering if there is a way I can apply a global modification to all
recipes in a layer? For instance, we have our own layer for our changes
that sit on top of the base Yocto/OE layers.
What if, hypothetically, I wanted to insert a do_package_qa action
globally, for everything in our layer.
