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

[Paul Eggleton]

Hi Alain,

On Friday, 24 March 2017 4:50:39 AM NZDT Alain Achkar wrote:
> 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 \

Something is wrong there - the SRC_URI field must not be being updated. For 
the most part the RRS is automatically populated. Anibal, any ideas?

> 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).

Backporting will require changes, definitely. You'll have to work through them 
- you may be able to use the migration information in the reference manual (in 
reverse, of course) to provide hints - the 2.2 (morty) and 2.1 (krogoth) 
sections would be appropriate for your situation:

http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#migration

You may also find the git history for the recipes in question to be 
instructive in terms of what changes were made to bring them to their current 
state in master.

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

You'd do that by checking out the branch in git and copying the entire 
directory, the RRS is just a reporting tool.

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

Since 3.6 isn't in master, there aren't any shortcuts I'm afraid, you would 
have to try manually updating it - probably the safest thing to do would be to 
copy the existing directory into your own custom layer and modify it there. I 
suspect starting at 3.5.2 is going to be fastest, but of course you'll need to 
backport that to jethro first.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre