docs/manual: clarify the <PKG>_PATCH_DEPENDENCIES guarantee

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>
This commit is contained in:
Baruch Siach 2020-02-21 07:34:42 +02:00 committed by Yann E. MORIN
parent 07fd2da595
commit d01e808bfe

View 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 * +LIBFOO_PATCH_DEPENDENCIES+ lists the dependencies (in terms of
package name) that are required for the current package to be package name) that are required for the current package to be
patched. These dependencies are guaranteed to be extracted and patched. These dependencies are guaranteed to be extracted and
patched before the current package is patched. In a similar way, patched (but not necessarily built) before the current package is
+HOST_LIBFOO_PATCH_DEPENDENCIES+ lists the dependencies for the patched. In a similar way, +HOST_LIBFOO_PATCH_DEPENDENCIES+ lists
current host package. the dependencies for the current host package.
This is seldom used; usually, +LIBFOO_DEPENDENCIES+ is what you This is seldom used; usually, +LIBFOO_DEPENDENCIES+ is what you
really want to use. really want to use.