|
@@ -7499,26 +7499,29 @@
|
|
|
</para>
|
|
|
|
|
|
<para>
|
|
|
- If a committed change results in changing the package output,
|
|
|
- then the value of the PR variable needs to be increased
|
|
|
- (or "bumped") as part of that commit.
|
|
|
+ If a committed change results in changing the package
|
|
|
+ output, then the value of the PR variable needs to be
|
|
|
+ increased (or "bumped") as part of that commit.
|
|
|
For new recipes you should add the <filename>PR</filename>
|
|
|
- variable and set its initial value equal to "r0", which is the default.
|
|
|
- Even though the default value is "r0", the practice of adding it to a new recipe makes
|
|
|
- it harder to forget to bump the variable when you make changes
|
|
|
- to the recipe in future.
|
|
|
+ variable and set its initial value equal to "r0", which is
|
|
|
+ the default.
|
|
|
+ Even though the default value is "r0", the practice of
|
|
|
+ adding it to a new recipe makes it harder to forget to bump
|
|
|
+ the variable when you make changes to the recipe in future.
|
|
|
</para>
|
|
|
|
|
|
<para>
|
|
|
- If you are sharing a common <filename>.inc</filename> file with multiple recipes,
|
|
|
- you can also use the
|
|
|
+ If you are sharing a common <filename>.inc</filename> file
|
|
|
+ with multiple recipes, you can also use the
|
|
|
<filename><ulink url='&YOCTO_DOCS_REF_URL;#var-INC_PR'>INC_PR</ulink></filename>
|
|
|
- variable to ensure that
|
|
|
- the recipes sharing the <filename>.inc</filename> file are rebuilt when the
|
|
|
+ variable to ensure that the recipes sharing the
|
|
|
+ <filename>.inc</filename> file are rebuilt when the
|
|
|
<filename>.inc</filename> file itself is changed.
|
|
|
- The <filename>.inc</filename> file must set <filename>INC_PR</filename>
|
|
|
- (initially to "r0"), and all recipes referring to it should set <filename>PR</filename>
|
|
|
- to "$(INC_PR).0" initially, incrementing the last number when the recipe is changed.
|
|
|
+ The <filename>.inc</filename> file must set
|
|
|
+ <filename>INC_PR</filename> (initially to "r0"), and all
|
|
|
+ recipes referring to it should set <filename>PR</filename>
|
|
|
+ to "${INC_PR}.0" initially, incrementing the last number
|
|
|
+ when the recipe is changed.
|
|
|
If the <filename>.inc</filename> file is changed then its
|
|
|
<filename>INC_PR</filename> should be incremented.
|
|
|
</para>
|
|
@@ -7527,14 +7530,14 @@
|
|
|
When upgrading the version of a package, assuming the
|
|
|
<filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PV'>PV</ulink></filename>
|
|
|
changes, the <filename>PR</filename> variable should be
|
|
|
- reset to "r0" (or "$(INC_PR).0" if you are using
|
|
|
+ reset to "r0" (or "${INC_PR}.0" if you are using
|
|
|
<filename>INC_PR</filename>).
|
|
|
</para>
|
|
|
|
|
|
<para>
|
|
|
Usually, version increases occur only to packages.
|
|
|
- However, if for some reason <filename>PV</filename> changes but does not
|
|
|
- increase, you can increase the
|
|
|
+ However, if for some reason <filename>PV</filename> changes
|
|
|
+ but does not increase, you can increase the
|
|
|
<filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PE'>PE</ulink></filename>
|
|
|
variable (Package Epoch).
|
|
|
The <filename>PE</filename> variable defaults to "0".
|
|
@@ -7544,7 +7547,8 @@
|
|
|
Version numbering strives to follow the
|
|
|
<ulink url='http://www.debian.org/doc/debian-policy/ch-controlfields.html'>
|
|
|
Debian Version Field Policy Guidelines</ulink>.
|
|
|
- These guidelines define how versions are compared and what "increasing" a version means.
|
|
|
+ These guidelines define how versions are compared and what
|
|
|
+ "increasing" a version means.
|
|
|
</para>
|
|
|
</section>
|
|
|
</section>
|