diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-09-26 14:39:02 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-10-01 22:52:54 +0100 |
| commit | 28144187dac0bb38d6a34e9b2640fb9f4dce6e10 (patch) | |
| tree | cfb6de8f00c3bc0ae21156532b9df97c79c2c08b | |
| parent | d8d58411887762f993492cb14642334a59b03a03 (diff) | |
| download | ast2050-yocto-poky-28144187dac0bb38d6a34e9b2640fb9f4dce6e10.zip ast2050-yocto-poky-28144187dac0bb38d6a34e9b2640fb9f4dce6e10.tar.gz | |
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>
| -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 af7eed3..83e5db3 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 83d4c1b..2743059 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> |
