diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index eb7ca69730..c75e718d67 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -3237,30 +3237,22 @@
post-installation script to be delayed until the first boot.
For example, the script might need to be executed on the
device itself.
- To delay script execution until boot time, use the following
- structure in the post-installation script:
-
- pkg_postinst_PACKAGENAME() {
- if [ x"$D" = "x" ]; then
- # Actions to carry out on the device go here
- else
- exit 1
- fi
- }
-
+ To delay script execution until boot time, you must explicitly
+ mark post installs to defer to the target.
+ You can use pkg_postinst_ontarget() or
+ call
+ postinst-intercepts defer_to_first_boot
+ from pkg_postinst().
+ Any failure of a pkg_postinst() script
+ (including exit 1) triggers an error during the
+ do_rootfs
+ task.
- The previous example delays execution until the image boots
- again because the environment variable D
- points to the directory containing the image when
- the root filesystem is created at build time but is unset
- when executed on the first boot.
-
-
-
- If you have recipes that use pkg_postinst
- scripts and they require the use of non-standard native
+ If you have recipes that use
+ pkg_postinst function
+ and they require the use of non-standard native
tools that have dependencies during rootfs construction, you
need to use the
PACKAGE_WRITE_DEPS
@@ -3279,8 +3271,8 @@
pkg_prerm, and
pkg_postrm, respectively.
These scrips work in exactly the same way as does
- pkg_postinst with the exception that they
- run at different times.
+ pkg_postinst with the exception
+ that they run at different times.
Also, because of when they run, they are not applicable to
being run at image creation time like
pkg_postinst.