diff options
Diffstat (limited to 'handbook/extendpoky.xml')
-rw-r--r-- | handbook/extendpoky.xml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/handbook/extendpoky.xml b/handbook/extendpoky.xml index cc0dc1fd25..f259d2ef0a 100644 --- a/handbook/extendpoky.xml +++ b/handbook/extendpoky.xml | |||
@@ -215,7 +215,7 @@ pkg_postinst_PACKAGENAME () { | |||
215 | <para> | 215 | <para> |
216 | Sometimes it is necessary that the execution of a post-installation | 216 | Sometimes it is necessary that the execution of a post-installation |
217 | script is delayed until the first boot, because the script | 217 | script is delayed until the first boot, because the script |
218 | needs to be executed the device itself. To delay script execution | 218 | needs to be executed on the device itself. To delay script execution |
219 | until boot time, the post-installation function should have the | 219 | until boot time, the post-installation function should have the |
220 | following structure: | 220 | following structure: |
221 | </para> | 221 | </para> |
@@ -268,7 +268,7 @@ inherit poky-image | |||
268 | 268 | ||
269 | <para> | 269 | <para> |
270 | By creating a custom image, a developer has total control | 270 | By creating a custom image, a developer has total control |
271 | over the contents of the image. It is important use | 271 | over the contents of the image. It is important to use |
272 | the correct names of packages in the <glossterm><link | 272 | the correct names of packages in the <glossterm><link |
273 | linkend='var-IMAGE_INSTALL'>IMAGE_INSTALL</link></glossterm> variable. | 273 | linkend='var-IMAGE_INSTALL'>IMAGE_INSTALL</link></glossterm> variable. |
274 | The names must be in | 274 | The names must be in |
@@ -295,11 +295,11 @@ IMAGE_INSTALL += "strace" | |||
295 | <title>Customising Images through custom tasks</title> | 295 | <title>Customising Images through custom tasks</title> |
296 | 296 | ||
297 | <para> | 297 | <para> |
298 | For for complex custom images, the best approach is to create a custom | 298 | For complex custom images, the best approach is to create a custom |
299 | task package which is them used to build the image (or images). A good | 299 | task package which is then used to build the image (or images). A good |
300 | example of a tasks package is <filename>meta/packages/tasks/task-poky.bb | 300 | example of a tasks package is <filename>meta/packages/tasks/task-poky.bb |
301 | </filename>. The <glossterm><link linkend='var-PACKAGES'>PACKAGES</link></glossterm> | 301 | </filename>. The <glossterm><link linkend='var-PACKAGES'>PACKAGES</link></glossterm> |
302 | variable lists the task packages to build (along with the complimentary | 302 | variable lists the task packages to build (along with the complementary |
303 | -dbg and -dev packages). For each package added, | 303 | -dbg and -dev packages). For each package added, |
304 | <glossterm><link linkend='var-PACKAGES'>RDEPENDS</link></glossterm> and | 304 | <glossterm><link linkend='var-PACKAGES'>RDEPENDS</link></glossterm> and |
305 | <glossterm><link linkend='var-PACKAGES'>RRECOMMENDS</link></glossterm> | 305 | <glossterm><link linkend='var-PACKAGES'>RRECOMMENDS</link></glossterm> |