diff --git a/bitbake/doc/manual/usermanual.xml b/bitbake/doc/manual/usermanual.xml
index e776b43c41..6781a71a62 100644
--- a/bitbake/doc/manual/usermanual.xml
+++ b/bitbake/doc/manual/usermanual.xml
@@ -137,6 +137,24 @@ share common metadata between many packages.
In this example, B is now bvaladditionaldata and C is testcval. In contrast to the above appending and prepending operators, no additional space
will be introduced.
+
+ Appending and Prepending (override style syntax)
+ B = "bval"
+B_append = " additional data"
+C = "cval"
+C_prepend = "additional data "
+ This example results in B becoming bval additional data
+and C becoming additional data cval. Note the spaces in the append.
+Unlike the += operator, additional space is not automatically added. You must take steps to add space
+yourself.
+
+
+ Removing (override style syntax)
+ FOO = "123 456 789 123456 123 456 123 456"
+FOO_remove = "123"
+FOO_remove = "456"
+ In this example, FOO is now 789 123456.
+
Conditional metadata set
OVERRIDES is a :
separated variable containing each item you want to satisfy conditions. So, if you have a variable which is conditional on arm
, and arm
is in OVERRIDES, then the arm
specific version of the variable is used rather than the non-conditional version. Example:
@@ -536,7 +554,7 @@ options:
Generating dependency graphs
BitBake is able to generate dependency graphs using the dot syntax. These graphs can be converted
-to images using the dot application from Graphviz.
+to images using the dot application from Graphviz.
Two files will be written into the current working directory, depends.dot containing dependency information at the package level and task-depends.dot containing a breakdown of the dependencies at the task level. To stop depending on common depends, one can use the -I depend to omit these from the graph. This can lead to more readable graphs. This way, DEPENDS from inherited classes such as base.bbclass can be removed from the graph.
$ bitbake -g blah
$ bitbake -g -I virtual/whatever -I bloom blah