From d01e808bfed8f76e084ec2899bd130a47fb020fa Mon Sep 17 00:00:00 2001 From: Baruch Siach Date: Fri, 21 Feb 2020 07:34:42 +0200 Subject: [PATCH] docs/manual: clarify the _PATCH_DEPENDENCIES guarantee Unlike _DEPENDENCIES, _PATCH_DEPENDENCIES only guarantees extract and patch of listed dependencies, not build. Make this subtlety more explicit in the documentation. Cc: Thomas De Schampheleire Signed-off-by: Baruch Siach [yann.morin.1998@free.fr: slight fix] Signed-off-by: Yann E. MORIN --- docs/manual/adding-packages-generic.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/manual/adding-packages-generic.txt b/docs/manual/adding-packages-generic.txt index 59cdb7ffd7..8ee51ca57d 100644 --- a/docs/manual/adding-packages-generic.txt +++ b/docs/manual/adding-packages-generic.txt @@ -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. -- 2.30.2