ref-manual: Updated ARCHIVER_MODE and archiver.bbclass
Added information in about the various varflags the user can use to define the type of archive. (From yocto-docs rev: 9035c415d4453750f016fe4ea2fa8179549330ca) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
4ec8e88a9a
commit
4764062664
|
@ -95,7 +95,8 @@
|
|||
section in the Yocto Project Development Manual.
|
||||
You can also see the
|
||||
<link linkend='var-ARCHIVER_MODE'><filename>ARCHIVER_MODE</filename></link>
|
||||
variable.
|
||||
variable for information about the variable flags (varflags)
|
||||
that help control archive creation.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
|
|
|
@ -295,7 +295,29 @@
|
|||
class, determines the type of information used to create
|
||||
a released archive.
|
||||
You can use this variable to create archives of patched
|
||||
source, original source, configured source, and so forth.
|
||||
source, original source, configured source, and so forth
|
||||
by employing the following variable flags (varflags):
|
||||
<literallayout class='monospaced'>
|
||||
ARCHIVER_MODE[src] = "original" # Uses original (unpacked) source
|
||||
# files.
|
||||
|
||||
ARCHIVER_MODE[src] = "patched" # Uses patched source files. This is
|
||||
# the default.
|
||||
|
||||
ARCHIVER_MODE[src] = "configured" # Uses configured source files.
|
||||
|
||||
ARCHIVER_MODE[diff] = "1" # Uses patches between do_unpack and
|
||||
# do_patch.
|
||||
|
||||
ARCHIVER_MODE[diff-exclude] ?= "<replaceable>file</replaceable> <replaceable>file</replaceable> ..." # Lists files and directories to
|
||||
# exclude from diff.
|
||||
|
||||
ARCHIVER_MODE[dumpdata] = "1" # Uses environment data.
|
||||
|
||||
ARCHIVER_MODE[recipe] = "1" # Uses recipe and include files.
|
||||
|
||||
ARCHIVER_MODE[srpm] = "1" # Uses RPM package files.
|
||||
</literallayout>
|
||||
For information on how the variable works, see the
|
||||
<filename>meta/classes/archiver.bbclass</filename> file
|
||||
in the
|
||||
|
|
Loading…
Reference in New Issue