From 7a26f2f66360ddbcf1be5833d4834a72ccde769f Mon Sep 17 00:00:00 2001 From: Samuel Martin Date: Thu, 28 Feb 2013 11:24:26 +0000 Subject: manual: minor fix in patch-policy.txt Signed-off-by: Samuel Martin Signed-off-by: Peter Korsgaard --- docs/manual/patch-policy.txt | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/manual/patch-policy.txt b/docs/manual/patch-policy.txt index 14c6efc53..0f55b26dc 100644 --- a/docs/manual/patch-policy.txt +++ b/docs/manual/patch-policy.txt @@ -34,12 +34,18 @@ Most patches are provided within Buildroot, in the package directory; these typically aim to fix cross-compilation, libc support, or other such issues. -These patch files should be named +-.patch+. +These patch files should be named +--.patch+. A +series+ file, as used by +quilt+, may also be added in the package directory. In that case, the +series+ file defines the patch application order. +.Notes +- The patch files coming with Buildroot should not contain any package version +reference in their filename. +- The field ++ in the patch file name refers to the 'apply order'. + + How patches are applied ~~~~~~~~~~~~~~~~~~~~~~~ @@ -56,8 +62,12 @@ How patches are applied * If a +series+ file exists in the package directory, then patches are applied according to the +series+ file; + -* Otherwise, patch files matching `-*.patch` are applied - following the +ls+ command order. +* Otherwise, patch files matching +-*.patch+ + are applied in alphabetical order. + So, to ensure they are applied in the right order, it is hightly + recommended to named the patch files like this: + +--.patch+, where ++ + refers to the 'apply order'. . Run the +_POST_PATCH_HOOKS+ commands if defined. -- cgit v1.2.3