sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

ref-manual: Minor edits to "Shared State Cache" section. 

(From yocto-docs rev: 73fa8a3f061bdefafd75373d266d87519a767602)

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 2013-03-26 11:42:01 -07:00 committed by Richard Purdie
parent bd11c55653
commit 881627ce68
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
documentation/ref-manual/technical-details.xml
View File

@ -156,7 +156,7 @@
<para>
By design, the OpenEmbedded build system builds everything from scratch unless
BitBake can determine that parts don't need to be rebuilt.
BitBake can determine that parts do not need to be rebuilt.
Fundamentally, building from scratch is attractive as it means all parts are
built fresh and there is no possibility of stale data causing problems.
When developers hit problems, they typically default back to building from scratch
@ -168,7 +168,7 @@
As mentioned in the previous paragraph, building from scratch ensures that
everything is current and starts from a known state.
However, building from scratch also takes much longer as it generally means
rebuilding things that don't necessarily need rebuilt.
rebuilding things that do not necessarily need rebuilt.
</para>
<para>
@ -178,7 +178,7 @@
<itemizedlist>
<listitem>What pieces of the system have changed and what pieces have not changed?</listitem>
<listitem>How are changed pieces of software removed and replaced?</listitem>
<listitem>How are pre-built components that don't need to be rebuilt from scratch
<listitem>How are pre-built components that do not need to be rebuilt from scratch
used when they are available?</listitem>
</itemizedlist>
</para>
@ -199,7 +199,7 @@
<note>
The OpenEmbedded build system does not maintain
<link linkend='var-PR'><filename>PR</filename></link> information
as part of the Shared State packages.
as part of the shared state packages.
Consequently, considerations exist that affect maintaining shared
state feeds.
For information on how the OpenEmbedded works with packages and can