From d022ec3ff5aff4cbee6b8aec677a1c03ca79705c Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 5 Feb 2014 08:15:37 -0600 Subject: bitbake: user-manual-ref-variables.xml: Edits to SRC_URI. (Bitbake rev: b8472f81387f8b8110cd560d61a4563d53d26859) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- bitbake/doc/user-manual/user-manual-ref-variables.xml | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/bitbake/doc/user-manual/user-manual-ref-variables.xml b/bitbake/doc/user-manual/user-manual-ref-variables.xml index 31e39ced7b..bda9fe5629 100644 --- a/bitbake/doc/user-manual/user-manual-ref-variables.xml +++ b/bitbake/doc/user-manual/user-manual-ref-variables.xml @@ -1872,16 +1872,15 @@ The list of source files - local or remote. This variable tells BitBake which bits - to pull in for the build and how to pull them in. - For example, if the recipe or append file only needs to - fetch a tarball from the Internet, the recipe or + to pull for the build and how to pull them. + For example, if the recipe or append file needs to + fetch a single tarball from the Internet, the recipe or append file uses a SRC_URI - entry that specifies just the tarball. + entry that specifies that tarball. On the other hand, if the recipe or append file needs to - fetch a tarball, apply two patches, and include a custom - file, the recipe or append file needs an - SRC_URI variable that specifies all - those sources. + fetch a tarball and include a custom file, the recipe or + append file needs an SRC_URI variable + that specifies all those sources. The following list explains the available URI protocols: file:// - -- cgit v1.2.3-54-g00ecf