1 files changed, 14 insertions, 12 deletions
diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml
index 46e7b79e75..cf77068e73 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -52,20 +52,22 @@
        and a C library as pre-requisites, and splitting out of debug symbols
        during packaging).
        <note>
-            Unlike e.g. Debian, OpenEmbedded recipes that produce packages
+            <para>Unlike some distro recipes (e.g. Debian), OpenEmbedded recipes
-            which
+            that produce packages that depend on tunings through use of the
            <link linkend='var-RDEPENDS'><filename>RDEPENDS</filename></link>
-            on
+            and
            <link linkend='var-TUNE_PKGARCH'><filename>TUNE_PKGARCH</filename></link>
-            packages should never be made <filename>allarch</filename>, even
+            variables, should never be configured for all architectures
-            if they do not produce architecture-specific output. This would
+            using <filename>allarch</filename>.
-            cause the do_package_write_* tasks to have different signatures
+            This is the case even if the recipes do not produce
-            for
+            architecture-specific output.</para>
-            <link linkend='var-MACHINE'><filename>MACHINE</filename></link>s
+            <para>Configuring such recipes for all architectures causes the
-            with different
+            <link linkend='ref-tasks-package_write_deb'><filename>do_package_write_*</filename></link>
-            <link linkend='var-TUNE_PKGARCH'><filename>TUNE_PKGARCH</filename></link>,
+            tasks to have different signatures for the machines with different
-            thus unnecessary rebuilds every single time an image for a different
+            tunings.
-            MACHINE is built (even without any change to the recipe).
+            Additionally, unnecessary rebuilds occur every time an
+            image for a different <filename>MACHINE</filename> is built
+            even when the recipe never changes.</para>
        </note>
    </para>

diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml index 46e7b79e75..cf77068e73 100644 --- a/documentation/ref-manual/ref-classes.xml +++ b/documentation/ref-manual/ref-classes.xml
@@ -52,20 +52,22 @@
52	and a C library as pre-requisites, and splitting out of debug symbols	52	and a C library as pre-requisites, and splitting out of debug symbols
53	during packaging).	53	during packaging).
54	<note>	54	<note>
55	Unlike e.g. Debian, OpenEmbedded recipes that produce packages	55	<para>Unlike some distro recipes (e.g. Debian), OpenEmbedded recipes
56	which	56	that produce packages that depend on tunings through use of the
57	<link linkend='var-RDEPENDS'><filename>RDEPENDS</filename></link>	57	<link linkend='var-RDEPENDS'><filename>RDEPENDS</filename></link>
58	on	58	and
59	<link linkend='var-TUNE_PKGARCH'><filename>TUNE_PKGARCH</filename></link>	59	<link linkend='var-TUNE_PKGARCH'><filename>TUNE_PKGARCH</filename></link>
60	packages should never be made <filename>allarch</filename>, even	60	variables, should never be configured for all architectures
61	if they do not produce architecture-specific output. This would	61	using <filename>allarch</filename>.
62	cause the do_package_write_* tasks to have different signatures	62	This is the case even if the recipes do not produce
63	for	63	architecture-specific output.</para>
64	<link linkend='var-MACHINE'><filename>MACHINE</filename></link>s	64	<para>Configuring such recipes for all architectures causes the
65	with different	65	<link linkend='ref-tasks-package_write_deb'><filename>do_package_write_*</filename></link>
66	<link linkend='var-TUNE_PKGARCH'><filename>TUNE_PKGARCH</filename></link>,	66	tasks to have different signatures for the machines with different
67	thus unnecessary rebuilds every single time an image for a different	67	tunings.
68	MACHINE is built (even without any change to the recipe).	68	Additionally, unnecessary rebuilds occur every time an
		69	image for a different <filename>MACHINE</filename> is built
		70	even when the recipe never changes.</para>
69	</note>	71	</note>
70	</para>	72	</para>
71		73