diff options
| -rw-r--r-- | documentation/ref-manual/migration.xml | 3 | ||||
| -rw-r--r-- | documentation/ref-manual/ref-classes.xml | 15 |
2 files changed, 18 insertions, 0 deletions
diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml index af7eed3892..83e5db3cd3 100644 --- a/documentation/ref-manual/migration.xml +++ b/documentation/ref-manual/migration.xml @@ -683,6 +683,9 @@ this check performed, you should add "version-going-backwards" to your value for one or the other variables depending on how you wish it to be handled. + See the documented QA checks in the + "<link linkend='ref-classes-insane'><filename>insane.bbclass</filename></link>" + section. </para></listitem> </itemizedlist> </para> diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml index 83d4c1bf85..2743059c0c 100644 --- a/documentation/ref-manual/ref-classes.xml +++ b/documentation/ref-manual/ref-classes.xml @@ -797,6 +797,21 @@ <listitem><para><emphasis><filename>perms:</filename></emphasis> Currently, this check is unused but reserved. </para></listitem> + <listitem><para><emphasis><filename>version-going-backwards:</filename></emphasis> + If Build History is enabled, reports when a package + being written out has a lower version than the previously + written package under the same name. + If you are placing output packages into a feed and + upgrading packages on a target system using that feed, the + version of a package going backwards can result in the target + system not correctly upgrading to the "new" version of the + package. + <note> + If you are not using runtime package management on your + target system, then you do not need to worry about + this situation. + </note> + </para></listitem> </itemizedlist> </para> </section> |