Change the handling of slave repositories to the usual notion of 'slave
overrides master'.

Signed-off-by: Michał Górny <mgo...@gentoo.org>
---
 glep-0072.rst | 22 ++++++++++++++--------
 1 file changed, 14 insertions(+), 8 deletions(-)

diff --git a/glep-0072.rst b/glep-0072.rst
index 9ad8b61..68b8e91 100644
--- a/glep-0072.rst
+++ b/glep-0072.rst
@@ -150,6 +150,20 @@ Testing means that the architecture does not use stable 
keywords at all.
 Presence of such keywords is considered an error.  Consistency is tested
 only for ``~arch``.
 
+arches.desc in slave repositories
+---------------------------------
+
+If ``arches.desc`` is present in several repositories, then each file affects
+packages in the repository in question.  If the file does not specify a value
+for given arch, the value from the master repository is used.  However, using
+it in multiple repositories is discouraged.
+
+Note that the stability status override affects only packages in the slave
+repository and their direct dependencies.  If an arch is set to ``testing``,
+then master repositories are still permitted to use stable keywords.  If it is
+set to ``stable``, then missing stable keywords in dependencies from the master
+repository will cause dependency graph inconsistency.
+
 
 Backwards Compatibility
 =======================
@@ -178,14 +192,6 @@ to determine a list of stable arches shall fall back to 
the current method
 of determining stable arches by scanning profiles.desc for stable profiles.
 
 
-arches.desc in overlays
-=======================
-
-If arches.desc is present in several repositories, then the strictest setting
-for an architecture wins. Using arches.desc outside the gentoo (or
-alternative) master repository however is discouraged.
-
-
 Copyright
 =========
 
-- 
2.26.0


Reply via email to