recipes-devtools/python/python3-transitions_0.9.3.bb add "native" support

[b4u-mw]

The package lacks support for "-native", so it cannot be used for running tests during build.

[OldManYellsAtCloud]

Would you mind sending a patch, or opening a PR with a fix?

[b4u-mw]

I checked the code but I'm not sure how to do it right.
I build with poky which brings some python3 packages (like python3-jinja2). These just have the line:

BBCLASSEXTEND = "native nativesdk"

With this I can just refer the python package as python3-jinja2-native so that it's available during tests on the build system.

But that class is part of poky which is not a dependency of meta-openembedded.

Edit: figured out that this is true for many (all?) openembedded python packages.

[OldManYellsAtCloud]

In general, this would be it, it is enough to add BBCLASSEXTEND = "native" to get a native version (and nativesdk is for the sdk version). There is one more requirement: the dependencies need to have a native version also (which is frequently the case) - you can try it easily by building the native version of your recipe. If Bitbake can't find a required dependency, it will complain about missing dependencies (in which case that dependency might need the BBCLASSEXTEND also in the recipe).

[b4u-mw]

I have created a PR for scarthgap (the branch I'm on). But how is it handled for all the other branches?