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 implement it, but wanted to make sure it was feasible. On Tue, Jul 10, 2018 at 2:27 PM Burton, Ross <ross.bur...@intel.com> wrote: > 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 <alex.kana...@gmail.com> > wrote: > > Yes. Implement a class and inherit it from the recipes. > > > > Alex > > > > 2018-07-10 20:50 GMT+02:00 Michael Habibi <mikehab...@gmail.com>: > >> 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. Is there a way to codify that, beyond > actually > >> adding this to every recipe in our layer? > >> > >> -- > >> _______________________________________________ > >> yocto mailing list > >> yocto@yoctoproject.org > >> https://lists.yoctoproject.org/listinfo/yocto > >> > > -- > > _______________________________________________ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
