summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-02-12 16:09:29 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-02-14 17:25:45 (GMT)
commita005cdaaedaadfeff8147bcb5050346314fd8bcb (patch)
tree04d2176de2f4b7a2a20947acfb6ad8ea7dd99ff3
parentee180d1475e247817ea898f89c0df422e2551616 (diff)
downloadpoky-a005cdaaedaadfeff8147bcb5050346314fd8bcb.tar.gz
dev-manual, ref-manual: Cross-references between PR Service and cache
Fixes YOCTO #3684 These changes help tie in the relationship between how the OE build system uses checksums and such and the PR Service that can track revision. (From yocto-docs rev: 39a3010a3bb4b2c1d37aef60984ac16e85b56aac) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml10
-rw-r--r--documentation/ref-manual/technical-details.xml12
2 files changed, 19 insertions, 3 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 1f8dba4..7e90eb8 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -2040,7 +2040,8 @@
2040 </para> 2040 </para>
2041 2041
2042 <para> 2042 <para>
2043 Because the OpenEmbedded build system uses "signatures", 2043 Because the OpenEmbedded build system uses
2044 "<ulink url='&YOCTO_DOCS_REF_URL;#checksums'>signatures</ulink>",
2044 which are unique to a given build, the build system 2045 which are unique to a given build, the build system
2045 knows when to rebuild packages. 2046 knows when to rebuild packages.
2046 All the inputs into a given task are represented by a 2047 All the inputs into a given task are represented by a
@@ -2128,7 +2129,7 @@
2128 </para> 2129 </para>
2129 2130
2130 <note> 2131 <note>
2131 The OpenEmbedded build system does not maintain 2132 <para>The OpenEmbedded build system does not maintain
2132 <filename>PR</filename> information as part of the 2133 <filename>PR</filename> information as part of the
2133 shared state (sstate) packages. 2134 shared state (sstate) packages.
2134 If you maintain an sstate feed, its expected that either 2135 If you maintain an sstate feed, its expected that either
@@ -2136,7 +2137,10 @@
2136 feed use a shared PR Service, or you do not run a PR 2137 feed use a shared PR Service, or you do not run a PR
2137 Service on any of your building systems. 2138 Service on any of your building systems.
2138 Having some systems use a PR Service while others do 2139 Having some systems use a PR Service while others do
2139 not leads to obvious problems. 2140 not leads to obvious problems.</para>
2141 <para>For more information on shared state, see the
2142 "<ulink url='&YOCTO_DOCS_REF_URL;#shared-state-cache'>Shared State Cache</ulink>"
2143 section in the Yocto Project Reference Manual.</para>
2140 </note> 2144 </note>
2141 </section> 2145 </section>
2142 2146
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index a9c31c8..3393e15 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -194,6 +194,18 @@
194 install them if they are deemed to be valid. 194 install them if they are deemed to be valid.
195 </para> 195 </para>
196 196
197 <note>
198 The OpenEmbedded build system does not maintain
199 <link linkend='var-PR'><filename>PR</filename></link> information
200 as part of the Shared State packages.
201 Consequently, considerations exist that affect maintaining shared
202 state feeds.
203 For information on how the OpenEmbedded works with packages and can
204 track incrementing <filename>PR</filename> information, see the
205 "<ulink url='&YOCTO_DOCS_DEV_URL;#incrementing-a-package-revision-number'>Incrementing a Package Revision Number</ulink>"
206 section.
207 </note>
208
197 <para> 209 <para>
198 The rest of this section goes into detail about the overall incremental build 210 The rest of this section goes into detail about the overall incremental build
199 architecture, the checksums (signatures), shared state, and some tips and tricks. 211 architecture, the checksums (signatures), shared state, and some tips and tricks.