From: Alexander Mukhin Date: Thu, 14 Sep 2017 14:47:42 +0000 (+0300) Subject: docs: clarify _PATCH behaviour X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=48934ed0a97b7baee7ad8fbfb19e449024cdda9d;p=buildroot.git docs: clarify _PATCH behaviour Reiterate once more that _PATCH variable can point to an arbitrary URL, not just to a path relative to _SITE. While we're at it, also explain that the patch should be added to the .hash file. Signed-off-by: Alexander Mukhin [Arnout: add sentence about .hash file.] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) --- diff --git a/docs/manual/patch-policy.txt b/docs/manual/patch-policy.txt index e1df8b003f..e704a0d3f3 100644 --- a/docs/manual/patch-policy.txt +++ b/docs/manual/patch-policy.txt @@ -19,9 +19,14 @@ global patch directory. ==== Downloaded If it is necessary to apply a patch that is available for download, then add it -to the +_PATCH+ variable. It is downloaded from the same site -as the package itself. It can be a single patch, or a tarball containing a -patch series. +to the +_PATCH+ variable. If an entry contains +://+, +then Buildroot will assume it is a full URL and download the patch +from this location. Otherwise, Buildroot will assume that the patch should be +downloaded from +_SITE+. It can be a single patch, +or a tarball containing a patch series. + +Like for all downloads, a hash should be added to the +.hash+ +file. This method is typically used for packages from Debian.