At the moment there is blacklist.bbclass implementation that is able to filter out recipe on global level. It would be good to have ability to filter recipe name or pattern of recipes if they are coming from specific layer. Or another example to implement layer specific "whitelist" of recipes to be used. For both of those, there is need to expose variable(s) that would be pointing beside $FILE or $PN from which layer name/path it's actually coming from.
I've pushed a branch with a patch that adds a function to bb.utils which does this: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=paule/stuff
Patch sent for review: http://patchwork.openembedded.org/patch/93813/
BTW, once it's get implemented, it would be good to also include in 1.8.x maintenance releases.
Sure, I've just sent a backport to bitbake 1.26, which will feed into the fido branch in poky when merged.
Now in the fido branch as well: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=fido&id=ca6ef30c7a33b3860d9b0d0da51d9b8786073170 Marking as resolved.
Hello, Checked this feature and it works. Steps performed to test it: 1)vi meta/recipes-tests/teste/teste_1.0.0.bb SUMARY = "test recipe" LICENSE = "CLOSED" python do_mytask(){ bb.note("running mytest") result = bb.utils.get_file_layer("/media/cosscat/Touro/5poky/meta/recipes-devtools/m4/m4_1.4.17.bb",d) bb.note(result) } addtask do_mytask before do_build 2) bitbake teste 3) cat log.do_mytask DEBUG: Executing python function do_mytask NOTE: running mytest NOTE: core DEBUG: Python function do_mytask finished Marking as verified. Costin