1 |
In Gentoo terms, 'testing' and 'unstable' are mostly synonymous, |
2 |
so using the two names for different purposes is confusing. Use |
3 |
'transitional' instead. |
4 |
|
5 |
Signed-off-by: Michał Górny <mgorny@g.o> |
6 |
--- |
7 |
glep-0072.rst | 25 +++++++++++++------------ |
8 |
1 file changed, 13 insertions(+), 12 deletions(-) |
9 |
|
10 |
diff --git a/glep-0072.rst b/glep-0072.rst |
11 |
index 0a9914b..1e906d2 100644 |
12 |
--- a/glep-0072.rst |
13 |
+++ b/glep-0072.rst |
14 |
@@ -56,7 +56,7 @@ a) An architecture loses its stable status (imagine c128), but |
15 |
about a broken stable dependency tree. If we do that, repoman does however |
16 |
also not check ~c128 consistency, meaning that the ~c128 dependency tree |
17 |
will soon be broken as well due to negligence. Given arches.conf as |
18 |
- described below, one could set the architecture c128 to "testing" status |
19 |
+ described below, one could set the architecture c128 to "transitional" status |
20 |
and keep stable profiles. This results in stable keywords being ignored, |
21 |
but consistency of the ~c128 dependency tree is still enforced. |
22 |
|
23 |
@@ -66,7 +66,7 @@ b) An architecture prepares for becoming a stable architecture (think arm64). |
24 |
as the stable dependency tree is not complete yet, the profiles need to be |
25 |
set to dev/exp, and again this brings the danger of the ~arm64 dependency |
26 |
tree getting inadvertently broken. Again the combination of setting the |
27 |
- architecture to "testing" in arches.desc and profiles to stable helps. |
28 |
+ architecture to "transitional" in arches.desc and profiles to stable helps. |
29 |
|
30 |
Finally, at the moment the "semi-official" algorithm to figure out if an |
31 |
architecture is stable in the colloquial sense (e.g., requires stabilization |
32 |
@@ -91,7 +91,8 @@ are ignored. Every blank line is ignored. Otherwise the file consists of two |
33 |
whitespace-separated columns: |
34 |
|
35 |
- first column: architecture name (keyword) |
36 |
-- second column: one of the three values ``stable``, ``testing``, ``unstable`` |
37 |
+- second column: one of the three values ``stable``, ``transitional``, |
38 |
+ ``unstable`` |
39 |
|
40 |
Additional columns are ignored to allow for future revisions of this document. |
41 |
|
42 |
@@ -99,16 +100,16 @@ An example arches.desc file might look as follows:: |
43 |
|
44 |
# Example arches.desc file |
45 |
amd64 stable |
46 |
- x86 stable # not for long |
47 |
+ x86 stable # not for long |
48 |
|
49 |
- mips testing |
50 |
- m68k unstable outdated |
51 |
+ sparc transitional |
52 |
+ m68k unstable outdated |
53 |
|
54 |
Initial value in the gentoo repository |
55 |
-------------------------------------- |
56 |
|
57 |
On introduction, the setting will be ``stable`` for all stable architectures, |
58 |
-``testing`` for all architectures where "inofficial" stable keywords are |
59 |
+``transitional`` for all architectures where "inofficial" stable keywords are |
60 |
maintained and are present in the repository by the arch teams (sh, s390, |
61 |
...), and ``unstable`` everywhere else. |
62 |
|
63 |
@@ -125,8 +126,8 @@ by profiles.desc (and ``-d`` / ``-e`` switches). |
64 |
This is the current behaviour and shall be the default if nothing is specified |
65 |
for an architecture. |
66 |
|
67 |
-testing |
68 |
-~~~~~~~ |
69 |
+transitional |
70 |
+~~~~~~~~~~~~ |
71 |
When a profile of an architecture is tested, then repoman treats ``arch`` |
72 |
in ebuilds as ``~arch``, and tests consistency only for ``~arch``. |
73 |
|
74 |
@@ -134,8 +135,8 @@ Which profiles of the arch are tested is still controlled by profiles.desc |
75 |
(and ``-d`` / ``-e`` switches). |
76 |
|
77 |
A new switch for repoman may be provided to temporarily upgrade |
78 |
-an architecture from ``testing`` to ``stable`` status (for architecture team |
79 |
-work). |
80 |
+an architecture from ``transitional`` to ``stable`` status (for architecture |
81 |
+team work). |
82 |
|
83 |
unstable |
84 |
~~~~~~~~ |
85 |
@@ -170,7 +171,7 @@ arches.desc present and old system |
86 |
Utilities ignore the unknown file. |
87 |
|
88 |
Repoman and other tools may emit surplus dependency errors when profiles are |
89 |
-checked on arches that are ``testing`` (they check the consistency |
90 |
+checked on arches that are ``transitional`` (they check the consistency |
91 |
of the stable tree alone, which may fail, since ``arch`` is supposed to be |
92 |
treated like ``~arch``). This affects only development work and can be fixed |
93 |
by updating repoman. |
94 |
-- |
95 |
2.26.0 |