docs/manual: clarify the <PKG>_PATCH_DEPENDENCIES guarantee
authorBaruch Siach <baruch@tkos.co.il>
Fri, 21 Feb 2020 05:34:42 +0000 (07:34 +0200)
committerYann E. MORIN <yann.morin.1998@free.fr>
Sun, 23 Feb 2020 08:30:27 +0000 (09:30 +0100)
Unlike <PKG>_DEPENDENCIES, <PKG>_PATCH_DEPENDENCIES only guarantees
extract and patch of listed dependencies, not build. Make this subtlety
more explicit in the documentation.

Cc: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
[yann.morin.1998@free.fr: slight fix]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
docs/manual/adding-packages-generic.txt

index 59cdb7ffd72da046c320f3c7d52f0220867cf8be..8ee51ca57d0040b3c91a7427ab9cb2ba5c5d5948 100644 (file)
@@ -374,9 +374,9 @@ not and can not work as people would expect it should:
 * +LIBFOO_PATCH_DEPENDENCIES+ lists the dependencies (in terms of
   package name) that are required for the current package to be
   patched. These dependencies are guaranteed to be extracted and
-  patched before the current package is patched. In a similar way,
-  +HOST_LIBFOO_PATCH_DEPENDENCIES+ lists the dependencies for the
-  current host package.
+  patched (but not necessarily built) before the current package is
+  patched. In a similar way, +HOST_LIBFOO_PATCH_DEPENDENCIES+ lists
+  the dependencies for the current host package.
   This is seldom used; usually, +LIBFOO_DEPENDENCIES+ is what you
   really want to use.