sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

ref-manual: Added the version-going-backwards test to insane 

Added this new test to the insane.bbclass section.  Also put
in a reference in the migration section back to the new
entry.

(From yocto-docs rev: 32e25547b439030b93d9bc72bdce916eded518b4)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-09-26 14:39:02 -07:00 committed by Richard Purdie
parent d8d5841188
commit 28144187da
2 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
documentation/ref-manual/migration.xml
View File

@ -683,6 +683,9 @@
this check performed, you should add this check performed, you should add
"version-going-backwards" to your value for one or the "version-going-backwards" to your value for one or the
other variables depending on how you wish it to be handled. 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> </para></listitem>
</itemizedlist> </itemizedlist>
</para> </para>

15
documentation/ref-manual/ref-classes.xml
View File

@ -797,6 +797,21 @@
<listitem><para><emphasis><filename>perms:</filename></emphasis> <listitem><para><emphasis><filename>perms:</filename></emphasis>
Currently, this check is unused but reserved. Currently, this check is unused but reserved.
</para></listitem> </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> </itemizedlist>
</para> </para>
</section> </section>