commit:     6f4d97c0db20af6e3d75063b118f3756983a589a
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Tue Feb 20 21:51:08 2018 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Mar 11 19:20:17 2018 +0000

glep-0068: Add <stabilize-allarches/> element to metadata.xml

Add a new <stabilize-allarches/> element to metadata.xml whose presence
can be used to indicate that the package is suitable for ALLARCHES
stabilization. Unlike the current system, this makes it possible to
easily determine when packages can be stabilized wrt ALLARCHES
independently of who requests the stabilization.

For example, in Python ecosystem there are some packages which have C
extensions or known-unportable code which we do not want to handle
through ALLARCHES. Right now we have to either remember them or recheck
for them when firing the stablereq, or — more commonly — we end up
not using ALLARCHES when we could.

Storing this information per-package will not only make it easier to
determine whether ALLARCHES is applicable but also introduce some
automation to determine that and react accordingly.

Approved on 2018-03-11 Council meeting.


 glep-0068.rst | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/glep-0068.rst b/glep-0068.rst
index e8cba5d..2e874e9 100644
--- a/glep-0068.rst
+++ b/glep-0068.rst
@@ -4,10 +4,10 @@ Title: Package and category metadata
 Author: Michał Górny <>
 Type: Standards Track
 Status: Final
-Version: 1
+Version: 1.1
 Created: 2016-03-14
-Last-Modified: 2017-05-05
-Post-History: 2016-03-16
+Last-Modified: 2018-03-11
+Post-History: 2018-02-20, 2016-03-16
 Content-Type: text/x-rst
 Requires: 67
 Replaces: 34, 46, 56
@@ -147,6 +147,13 @@ element can contain, in any order:
   languages (at most one for each language), as detailed
   in `Slot descriptions`_.
+- zero or more ``<stabilize-allarches/>`` elements, possibly restricted
+  to specific package versions (at most one for each version) whose presence
+  indicates that the appropriate ebuilds are suitable for simultaneously
+  marking stable on all architectures where a previous version is stable
+  after arch testing on one of them (i.e. if the package is known to be fully
+  arch-independent).
 - zero or more ``<use/>`` elements containing USE flag descriptions
   in different languages (at most one for each language), as detailed
   in `USE flag descriptions`_.

Reply via email to