This point came up multiple times in the past and the special handling
of targetinstall stages lead to confusion when trying to depend on image
packages. Document it to prevent further confusion in that matter.
Signed-off-by: Roland Hieber <r...@pengutronix.de>
---
doc/ref_rule_file_layout.inc | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/doc/ref_rule_file_layout.inc b/doc/ref_rule_file_layout.inc
index ea7eb8c4903d..f58b07b44817 100644
--- a/doc/ref_rule_file_layout.inc
+++ b/doc/ref_rule_file_layout.inc
@@ -23,6 +23,18 @@ Each rule file provides PTXdist with the required steps (in
PTXdist called
- targetinstall.post
+.. note::
+
+ Host and image packages don't need to install anything in the target file
system.
+ Therefore, PTXdist only respects the *targetinstall* and *targetinstall.post*
+ stages for packages whose name doesn't start with ``host-`` or ``image-``.
+
+ When you want to depend on the output of a certain image package, you can
+ usually use its image name as an `additional prerequisite
<make-prereq-types_>`_
+ in your make rule for the dependent stage.
+
+.. _make-prereq-types:
https://www.gnu.org/software/make/manual/make.html#Prerequisite-Types
+
Default stage rules
~~~~~~~~~~~~~~~~~~~
--
2.20.1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
