diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml index 42ea19f3fc..ade91e94f1 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml @@ -217,11 +217,12 @@ Where the source code resides and how to fetch it Whether the source code requires - any patches + any patches, where to find them, and how to apply + them How to configure and compile the source code Where on the target machine to install the - package or packages being compiled + package or packages created @@ -233,7 +234,11 @@ The term "package" is also commonly used to describe recipes. However, since the same word is used to describe packaged output from a project, it is best to maintain a single - descriptive term, "recipes". + descriptive term - "recipes". + Put another way, a single "recipe" file is quite capable + of generating a number of related but separately installable + "packages". + In fact, that ability is fairly common. @@ -318,7 +323,6 @@ Append files, which are files that have the .bbappend file extension, extend or override information in an existing recipe file. - recipe file. @@ -331,8 +335,9 @@ - Information in append files overrides the information in the - similarly-named recipe file. + Information in append files extends or + overrides the information in the underlying, + similarly-named recipe files. @@ -357,6 +362,12 @@ However, if you named the append file busybox_1.%.bbappend, then you would have a match. + + + In the most general case, you could name the append file something as + simple as busybox_%.bbappend to be entirely + version independent. + @@ -437,7 +448,7 @@ has been thoroughly tested for compatibility with the other components. For information on how to check out a particular BitBake-based - build system, the build system's supporting documentation. + build system, consult that build system's supporting documentation.