dev-manual: Updated the "Core System Development" section
Added a new bullet as a tip for best practices that addresses how we address bug 3071 and 3274. We are suggesting they enable a PR Service if they are using continually incrementing PR values when package feeds are published or used. Reported-by: Richard Purdie <richard.purdie@linux.com> (From yocto-docs rev: b90497f139b1b6f7ab5510313eb297d5d7fb4e68) 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
89fa4b26c7
commit
315a3156e1
|
@ -185,6 +185,17 @@
|
|||
extensive testing while they continue to develop
|
||||
locally using their primary development system.
|
||||
</para></listitem>
|
||||
<listitem><para>Enable the PR Service when package feeds
|
||||
need to be incremental with continually increasing
|
||||
<ulink url='&YOCTO_DOCS_REF_URL;#var-PR'>PR</ulink>
|
||||
values.
|
||||
Typically, this situation occurs when you use or
|
||||
publish package feeds and use a shared state.
|
||||
You should enable the PR Service for all users who
|
||||
use the shared state pool.
|
||||
For more information on the PR Service, see the
|
||||
"<link linkend='working-with-a-pr-service'>Working With a PR Service</link>".
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
</section>
|
||||
|
|
Loading…
Reference in New Issue