summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-11-06 10:58:42 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-12-03 12:53:05 +0000
commit437bf60876e53d4f56598f5e51301a8b437c5c5d (patch)
treef5d9ad54d9abd61476968e0fd6785af2a07ee08a /documentation/ref-manual
parentc354dc6e4fe903bf3c287eed0318c5107a9d8c2e (diff)
downloadpoky-437bf60876e53d4f56598f5e51301a8b437c5c5d.tar.gz
ref-manual: Tweaks to a patch from Robert P. J. Day
I altered three areas from the previous patch submitted and applied from Robert P. J. Day. Two minor wording changes and removal of negative language. (From yocto-docs rev: 0212b01f82637c3498f26bce57e98508c84799c5) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual')
-rw-r--r--documentation/ref-manual/technical-details.xml9
1 files changed, 5 insertions, 4 deletions
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index f863c4cfb7..4d1c2e3f4e 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -60,7 +60,8 @@
60 and is responsible for parsing the 60 and is responsible for parsing the
61 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>, 61 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>,
62 generating a list of tasks from it, and then executing those tasks. 62 generating a list of tasks from it, and then executing those tasks.
63 To see a list of the options BitBake supports, use either of: 63 To see a list of the options BitBake supports, use either of
64 the following commands:
64 <literallayout class='monospaced'> 65 <literallayout class='monospaced'>
65 $ bitbake -h 66 $ bitbake -h
66 $ bitbake --help 67 $ bitbake --help
@@ -112,13 +113,13 @@
112 The <filename>.bb</filename> files are usually referred to as "recipes." 113 The <filename>.bb</filename> files are usually referred to as "recipes."
113 In general, a recipe contains information about a single piece of software. 114 In general, a recipe contains information about a single piece of software.
114 This information includes the location from which to download the 115 This information includes the location from which to download the
115 pristine source, any source patches to be applied to that source 116 unaltered source, any source patches to be applied to that source
116 (if any are needed), which special configuration options to apply, 117 (if needed), which special configuration options to apply,
117 how to compile the source files, and how to package the compiled output. 118 how to compile the source files, and how to package the compiled output.
118 </para> 119 </para>
119 120
120 <para> 121 <para>
121 The term "package" is sometimes (confusingly) used to refer to recipes. However, 122 The term "package" is sometimes used to refer to recipes. However,
122 since the word "package" is used for the packaged output from the OpenEmbedded 123 since the word "package" is used for the packaged output from the OpenEmbedded
123 build system (i.e. <filename>.ipk</filename> or <filename>.deb</filename> files), 124 build system (i.e. <filename>.ipk</filename> or <filename>.deb</filename> files),
124 this document avoids using the term "package" when referring to recipes. 125 this document avoids using the term "package" when referring to recipes.