dev-manual: Edits to add more detail to where patch files are

Updated some text to indicate that you should put patch files
in $BP, $BPN, or "files."  Also, added more on how the patch
files suffix is (i.e. accounting for compressed suffix names
like diff.bz).

Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: d9e23da24e9d86ec5e2b9d4067667478f3e56ba1)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2015-01-19 10:14:16 -08:00 committed by Richard Purdie
parent 6a6687d6d5
commit 281c4728d6
1 changed files with 6 additions and 2 deletions

View File

@ -1935,7 +1935,9 @@
fetched.
Any files mentioned in <filename>SRC_URI</filename> whose
names end in <filename>.patch</filename> or
<filename>.diff</filename> are treated as patches.
<filename>.diff</filename> or compressed versions of these
suffixes (e.g. <filename>diff.gz</filename> are treated as
patches.
The
<ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-patch'><filename>do_patch</filename></ulink>
task automatically applies these patches.
@ -1959,7 +1961,9 @@
using <filename>file://</filename>, you should place
patch files in a directory next to the recipe either
named the same as the base name of the recipe
(<ulink url='&YOCTO_DOCS_REF_URL;#var-BPN'><filename>BPN</filename></ulink>),
(<ulink url='&YOCTO_DOCS_REF_URL;#var-BP'><filename>BP</filename></ulink>
and
<ulink url='&YOCTO_DOCS_REF_URL;#var-BPN'><filename>BPN</filename></ulink>)
or "files".
</para>
</section>