[yocto] How to interpret the "Recipes reporting system" (e.g. for Python3 3.4, 3.5, 3.6)

Alain Achkar alain.achkar at triacta.com
Thu Mar 23 08:50:39 PDT 2017


Hello!

Is there any brief README or documentation about the "Recipe reporting
system" ?

For example: http://recipes.yoctoproject.org/rrs/recipedetail/297/

Is it automatically generated or manually maintained? (If you look at the
field Source URI, it points to Python-3.4.3.tar.xz but the Recipe file
points to python3_3.5.3.bb which contains:

SRC_URI = "http://www.python.org/ftp/python/${PV}/Python-${PV}.tar.xz \



I am trying to understand how/if I can use it. For example, if I am using
Jethro and I want Python 3.5 or 3.6, how can I use the "Recipe reporting
system" to achieve this? (I don't want to upgrade to Krogoth or Morty)

In Jethro, I have:


*poky/meta/recipes-devtools/python/python3_3.4.3.bb
<http://python3_3.4.3.bb>*

which of course builds Python 3.4

I know that if I download Morty, I get:

*poky/meta/recipes-devtools/python/python3_3.5.2.bb
<http://python3_3.5.2.bb>*

so, I tried copying this recipe into my Jethro source tree (at the same
location) but I got too many errors (I think there are several patches that
are needed).

So, is it possible to use the "Recipe reporting system" to see changes in
another branch and bring them in to my branch?

Moreover, if Python 3.6 is not available in Morty, how can I make a recipe
for it?

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170323/a8eb98d8/attachment.html>


More information about the yocto mailing list