dev-manual: Updated PR Service section with comments
Fixes YOCTO #2684 Applied some review comments to the section from Richard Purdie. (From yocto-docs rev: 772617a45df10e5e42364854fe03d8aad7cb46b6) 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
ba9fc8aaf3
commit
b8761468d3
|
@ -2070,10 +2070,11 @@
|
|||
</para>
|
||||
|
||||
<para>
|
||||
By default, there is no server that runs the PR Service.
|
||||
By default, the PR Service is not enabled or running.
|
||||
Thus, the packages generated are just "self consistent".
|
||||
The build system adds and removes packages and
|
||||
there are no guarantees about upgrade paths.
|
||||
there are no guarantees about upgrade paths but images
|
||||
will be consistent and correct with the latest changes.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
@ -2187,19 +2188,6 @@
|
|||
Debian Version Field Policy Guidelines</ulink>.
|
||||
These guidelines define how versions are compared and what "increasing" a version means.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
There are two reasons for following the previously mentioned guidelines.
|
||||
First, to ensure that when a developer updates and rebuilds, they get all the changes to
|
||||
the repository and do not have to remember to rebuild any sections.
|
||||
Second, to ensure that target users are able to upgrade their
|
||||
devices using package manager commands such as <filename>opkg upgrade</filename>
|
||||
(or similar commands for dpkg/apt or rpm-based systems).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The goal is to ensure the Yocto Project has packages that can be upgraded in all cases.
|
||||
</para>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
|
|
Loading…
Reference in New Issue