aboutsummaryrefslogtreecommitdiffstats
path: root/docs/usermanual/reference/var_src_uri.xml
diff options
context:
space:
mode:
Diffstat (limited to 'docs/usermanual/reference/var_src_uri.xml')
-rw-r--r--docs/usermanual/reference/var_src_uri.xml51
1 files changed, 36 insertions, 15 deletions
diff --git a/docs/usermanual/reference/var_src_uri.xml b/docs/usermanual/reference/var_src_uri.xml
index b858e8abb0..95632569dd 100644
--- a/docs/usermanual/reference/var_src_uri.xml
+++ b/docs/usermanual/reference/var_src_uri.xml
@@ -2,7 +2,7 @@
<section id="src_uri_variable" xreflabel="SRC_URI variable">
<title>SRC_URI variable: Source code and patches</title>
- <para>All recipies need to contain a definition of
+ <para>All recipes need to contain a definition of
<command>SRC_URI</command>. It determines what files and source code is
needed and where that source code should be obtained from. This includes
patches to be applied and basic files that are shipped as part of the
@@ -10,8 +10,8 @@
<para>A typical <command>SRC_URI</command> contains a list of URL's, patches
and files as shown in this example from quagga:<screen>SRC_URI = "http://www.quagga.net/download/quagga-${PV}.tar.gz \
- file://ospfd-no-opaque-lsa-fix.patch;patch=1 \
- file://fix-for-lib-inpath.patch;patch=1 \
+ file://ospfd-no-opaque-lsa-fix.patch \
+ file://fix-for-lib-inpath.patch \
file://quagga.init \
file://quagga.default \
file://watchquagga.init \
@@ -37,13 +37,13 @@ SRC_URI[sha256sum] = &quot;36bdb85c97b39ac604bc58cb7857ee08295242c78a12848ef8a31
a checksum will throw errors.</para>
<para>Each URI supports a set of additional options. These options are
tag/value pairs of the form <command>"a=b"</command> and are semi-colon
- separated from each other and from the URI. The follow examples shows two
- options being included, the patch and pnum options:<screen>file://ospfd-no-opaque-lsa-fix.patch;patch=1;pnum=2</screen>The
+ separated from each other and from the URI. The following example shows one
+ option being included, the striplevel option:<screen>file://ospfd-no-opaque-lsa-fix.patch;striplevel=2</screen>The
supported methods for fetching source and files are:</para>
<variablelist>
<varlistentry>
- <term>http, https, ftps</term>
+ <term>http, https, ftp, ftps</term>
<listitem>
<para>Used to download files and source code via the specified URL.
@@ -113,7 +113,7 @@ SRC_URI[sha256sum] = &quot;36bdb85c97b39ac604bc58cb7857ee08295242c78a12848ef8a31
</varlistentry>
<varlistentry>
- <term>.tbz, .tar.bz2</term>
+ <term>.tbz, .tbz2, .tar.bz2</term>
<listitem>
<para>Bzip2 compressed tar archives which will be extracted with
@@ -143,7 +143,25 @@ SRC_URI[sha256sum] = &quot;36bdb85c97b39ac604bc58cb7857ee08295242c78a12848ef8a31
</varlistentry>
<varlistentry>
- <term>.zip</term>
+ <term>.xz</term>
+
+ <listitem>
+ <para>xz (LZMA2) compressed files which will be decompressed with
+ <command>"xz -dc &lt;srcfile&gt; &gt; &lt;srcfile&gt;"</command>.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>.tar.xz</term>
+
+ <listitem>
+ <para>xz (LZMA2) compressed tar archives which will be decompressed with
+ <command>"xz -dc &lt;srcfile&gt; | tar x --no-same-owner -f -"</command>.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>.zip, .jar</term>
<listitem>
<para>Zip archives which will be extracted with <command>"unzip -q
@@ -209,7 +227,7 @@ SRC_URI[sha256sum] = &quot;36bdb85c97b39ac604bc58cb7857ee08295242c78a12848ef8a31
scripts, to be included in the final package.</para>
<para>The following example shows the specification of a patch
- file:<screen>file://ospfd-no-opaque-lsa-fix.patch;patch=1</screen></para>
+ file:<screen>file://ospfd-no-opaque-lsa-fix.patch</screen></para>
<para>Patch files are be copied to the patches subdirectory of the source
directory, <command>${S}/patches</command>, and then applied from the
@@ -234,18 +252,21 @@ SRC_URI[sha256sum] = &quot;36bdb85c97b39ac604bc58cb7857ee08295242c78a12848ef8a31
<variablelist>
<varlistentry>
- <term>patch</term>
+ <term>apply={yes|no}</term>
<listitem>
- <para>Used as <command>"patch=1"</command> to define this file as a
- patch file. Patch files will be copied to
+ <para>If set to 'yes' it is used as <command>"patch=1"</command> to define this file as a
+ patch file. Patch files will be symlinked into
<command>${S}/patches</command> and then applied to source from
- within the source directory, <command>${S}</command>.</para>
+ within the source directory, <command>${S}</command>.
+ If set to 'no' the file will be copied to <command>${S}</command>
+ during unpack.
+ </para>
</listitem>
</varlistentry>
<varlistentry>
- <term>pnum</term>
+ <term>striplevel</term>
<listitem>
<para>By default patches are applied with the <command>"-p
@@ -254,7 +275,7 @@ SRC_URI[sha256sum] = &quot;36bdb85c97b39ac604bc58cb7857ee08295242c78a12848ef8a31
the value passed to <command>"-p"</command>. The most typical use is
when the patches are relative to the source directory already and
need to be applied using <command>"-p 0"</command>, in which case
- the <command>"pnum=0"</command> option is supplied.</para>
+ the <command>"striplevel=0"</command> option is supplied.</para>
</listitem>
</varlistentry>
</variablelist>