diff options
author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2024-02-21 22:14:35 +0100 |
---|---|---|
committer | Steve Sakoman <steve@sakoman.com> | 2024-03-13 03:59:26 -1000 |
commit | 3d5846e144e4446b08bd9cff958f6beb8c116bf4 (patch) | |
tree | 67573310a0cffe7edb3019c84d7802571e73b91d | |
parent | d241202fa1f02e537c29e4ec5bbba945f957ede5 (diff) | |
download | poky-3d5846e144e4446b08bd9cff958f6beb8c116bf4.tar.gz |
dev-manual: packages: clarify shared PR service constraint
Explicit the problems previous described as "obvious".
(From yocto-docs rev: c5e3b57398d98626e348cb14d2a89ecc5f424dd4)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Suggested-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
-rw-r--r-- | documentation/dev-manual/packages.rst | 11 |
1 files changed, 8 insertions, 3 deletions
diff --git a/documentation/dev-manual/packages.rst b/documentation/dev-manual/packages.rst index 0e991e409a..d90ff7110e 100644 --- a/documentation/dev-manual/packages.rst +++ b/documentation/dev-manual/packages.rst | |||
@@ -205,9 +205,14 @@ history, see the | |||
205 | The OpenEmbedded build system does not maintain :term:`PR` information as | 205 | The OpenEmbedded build system does not maintain :term:`PR` information as |
206 | part of the shared state (sstate) packages. If you maintain an sstate | 206 | part of the shared state (sstate) packages. If you maintain an sstate |
207 | feed, it's expected that either all your building systems that | 207 | feed, it's expected that either all your building systems that |
208 | contribute to the sstate feed use a shared PR Service, or you do not | 208 | contribute to the sstate feed use a shared PR service, or you do not |
209 | run a PR Service on any of your building systems. Having some systems | 209 | run a PR Service on any of your building systems. |
210 | use a PR Service while others do not leads to obvious problems. | 210 | |
211 | That's because if you had multiple machines sharing a PR service but | ||
212 | not their sstate feed, you could end up with "diverging" hashes for | ||
213 | the same output artefacts. When presented to the share PR service, | ||
214 | each would be considered as new and would increase the revision | ||
215 | number, causing many unnecessary package upgrades. | ||
211 | 216 | ||
212 | For more information on shared state, see the | 217 | For more information on shared state, see the |
213 | ":ref:`overview-manual/concepts:shared state cache`" | 218 | ":ref:`overview-manual/concepts:shared state cache`" |