ref-manual: Review edits to the AUTOREV variable.
Fixes [YOCTO #7306] Some review updates to have better wording. (From yocto-docs rev: 6f2d10c87128934958295111d10e038689fd94d3) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
f03c8374a9
commit
51bdf3ba5f
|
@ -408,18 +408,20 @@
|
|||
</para>
|
||||
|
||||
<para>
|
||||
If you use the previous statement to inherit the latest
|
||||
If you use the previous statement to retrieve the latest
|
||||
version of software, you need to be sure
|
||||
<link linkend='var-PV'><filename>PV</filename></link>
|
||||
contains
|
||||
<filename>${</filename><link linkend='var-SRCPV'><filename>SRCPV</filename></link><filename>}</filename>.
|
||||
For example, suppose you have a kernel recipe that needs
|
||||
to inherit the latest kernel and you use the previous
|
||||
statement.
|
||||
For example, suppose you have a kernel recipe that
|
||||
inherits the
|
||||
<link linkend='ref-classes-kernel'>kernel</link> class
|
||||
and you use the previous statement.
|
||||
In this example, <filename>${SRCPV}</filename> does not
|
||||
get into <filename>PV</filename>.
|
||||
automatically get into <filename>PV</filename>.
|
||||
Consequently, you need to change <filename>PV</filename>
|
||||
so that it does contain <filename>${SRCPV}</filename>.
|
||||
in your recipe so that it does contain
|
||||
<filename>${SRCPV}</filename>.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
|
Loading…
Reference in New Issue