1 |
Add a new <stabilize-allarches/> element to metadata.xml whose presence |
2 |
can be used to indicate that the package is suitable for ALLARCHES |
3 |
stabilization. Unlike the current system, this makes it possible to |
4 |
easily determine when packages can be stabilized wrt ALLARCHES |
5 |
independently of who requests the stabilization. |
6 |
|
7 |
For example, in Python ecosystem there are some packages which have C |
8 |
extensions or known-unportable code which we do not want to handle |
9 |
through ALLARCHES. Right now we have to either remember them or recheck |
10 |
for them when firing the stablereq, or — more commonly — we end up |
11 |
not using ALLARCHES when we could. |
12 |
|
13 |
Storing this information per-package will not only make it easier to |
14 |
determine whether ALLARCHES is applicable but also introduce some |
15 |
automation to determine that and react accordingly. |
16 |
--- |
17 |
glep-0068.rst | 11 ++++++++--- |
18 |
1 file changed, 8 insertions(+), 3 deletions(-) |
19 |
|
20 |
diff --git a/glep-0068.rst b/glep-0068.rst |
21 |
index e8cba5d..f1f9ff5 100644 |
22 |
--- a/glep-0068.rst |
23 |
+++ b/glep-0068.rst |
24 |
@@ -4,10 +4,10 @@ Title: Package and category metadata |
25 |
Author: Michał Górny <mgorny@g.o> |
26 |
Type: Standards Track |
27 |
Status: Final |
28 |
-Version: 1 |
29 |
+Version: 1.1 |
30 |
Created: 2016-03-14 |
31 |
-Last-Modified: 2017-05-05 |
32 |
-Post-History: 2016-03-16 |
33 |
+Last-Modified: 2018-02-20 |
34 |
+Post-History: 2018-02-20, 2016-03-16 |
35 |
Content-Type: text/x-rst |
36 |
Requires: 67 |
37 |
Replaces: 34, 46, 56 |
38 |
@@ -147,6 +147,11 @@ element can contain, in any order: |
39 |
languages (at most one for each language), as detailed |
40 |
in `Slot descriptions`_. |
41 |
|
42 |
+- zero or more ``<stabilize-allarches/>`` elements, possibly restricted |
43 |
+ to specific package versions (at most one for each version) whose presence |
44 |
+ indicates that the appropriate ebuilds are suitable for ALLARCHES |
45 |
+ stabilization. |
46 |
+ |
47 |
- zero or more ``<use/>`` elements containing USE flag descriptions |
48 |
in different languages (at most one for each language), as detailed |
49 |
in `USE flag descriptions`_. |
50 |
-- |
51 |
2.16.2 |