I'm using SRCREV = "${AUTOREV}" in a kernel recipe (inheriting kernel, so ${SRCPV} is in PV). The latest version of my kernel is only fetched if I change my defconfig. Using bitbake virtual/kernel twice doesn't even go through srcrev_internal_helper().
Actually, the kernel class is not putting ${SRCPV} in PV. Doing that solved the issue. It may be good to update the documentation.
Hi, I was alerted to the fact that we need some documentation changes here for this issue. I have updated two variables in the glossary to try to explain this issue. You can see them at: http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-AUTOREV http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-SRCREV Please look the changes over and let me know if they are okay. Thanks, Scott
Hi, I'm not sure you should actually mention the kernel class at all, the comment about having PV containing SRCPV is valid for all recipes.
Hi, Based on feedback, see the links now. http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-AUTOREV http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-SRCREV thanks, Scott
For AUTOREV, what about: If you use the previous statement to retrieve the latest version of software, you need to be sure PV contains ${SRCPV}. For example, suppose you have a kernel recipe that inherits the kernel class and you use the previous statement. In this example, ${SRCPV} does not automatically get into PV. Consequently, you need to change PV in your recipe so that it does contain ${SRCPV}.
Alexandre, I like your wording. I have taken it verbatim. You can re-check the link and see the update. Thanks, Scott
I'm fine with that change (obviously !)
Hi, Unsure as to how to indicate the docs have been completed for this issue. The actual state has been set to RESOLVED/INVALID and I have the documentation flag set to "done." I guess this comment here basically acknowledges that the change was looked at and approved by Alexandre. I am done with it. Thanks, Scott