From ea5fa49bfc7ee42887ebaa32e600336b7d7a0ebd Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Wed, 21 Feb 2024 22:14:35 +0100 Subject: dev-manual: packages: clarify shared PR service constraint Explicit the problems previous described as "obvious". (From yocto-docs rev: ca939f9ceebbf9b5e82bb76abf1c4d20f039d68e) Signed-off-by: Michael Opdenacker Suggested-by: Richard Purdie Signed-off-by: Richard Purdie --- documentation/dev-manual/packages.rst | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) (limited to 'documentation/dev-manual') 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 The OpenEmbedded build system does not maintain :term:`PR` information as part of the shared state (sstate) packages. If you maintain an sstate feed, it's expected that either all your building systems that - contribute to the sstate feed use a shared PR Service, or you do not - run a PR Service on any of your building systems. Having some systems - use a PR Service while others do not leads to obvious problems. + contribute to the sstate feed use a shared PR service, or you do not + run a PR Service on any of your building systems. + + That's because if you had multiple machines sharing a PR service but + not their sstate feed, you could end up with "diverging" hashes for + the same output artefacts. When presented to the share PR service, + each would be considered as new and would increase the revision + number, causing many unnecessary package upgrades. For more information on shared state, see the ":ref:`overview-manual/concepts:shared state cache`" -- cgit v1.2.3-54-g00ecf