| 1 |
Remove the policy part from GLEP 81, making it into a pure technical |
| 2 |
specification. The policy will now be defined by the QA team |
| 3 |
as a regular tree policy. Since the planned policy updates make it |
| 4 |
less restrictive, there is really no need to hammer it at GLEP level. |
| 5 |
|
| 6 |
Signed-off-by: Michał Górny <mgorny@g.o> |
| 7 |
--- |
| 8 |
glep-0081.rst | 48 +++++++++++++----------------------------------- |
| 9 |
1 file changed, 13 insertions(+), 35 deletions(-) |
| 10 |
|
| 11 |
diff --git a/glep-0081.rst b/glep-0081.rst |
| 12 |
index 41db473..5218fa4 100644 |
| 13 |
--- a/glep-0081.rst |
| 14 |
+++ b/glep-0081.rst |
| 15 |
@@ -5,10 +5,10 @@ Author: Michał Górny <mgorny@g.o>, |
| 16 |
Michael Orlitzky <mjo@g.o> |
| 17 |
Type: Standards Track |
| 18 |
Status: Final |
| 19 |
-Version: 1 |
| 20 |
+Version: 1.1 |
| 21 |
Created: 2019-05-29 |
| 22 |
-Last-Modified: 2019-10-07 |
| 23 |
-Post-History: 2019-05-29, 2019-07-08 |
| 24 |
+Last-Modified: 2019-12-10 |
| 25 |
+Post-History: 2019-05-29, 2019-07-08, 2019-12-10 |
| 26 |
Content-Type: text/x-rst |
| 27 |
Replaces: 27 |
| 28 |
--- |
| 29 |
@@ -22,6 +22,14 @@ accounts. Dependencies are used to request users and group from within |
| 30 |
regular packages, and to track their usage. |
| 31 |
|
| 32 |
|
| 33 |
+Changes |
| 34 |
+======= |
| 35 |
+ |
| 36 |
+v1.1 |
| 37 |
+ The policy part was removed from the GLEP, in order to make it a tree |
| 38 |
+ policy. The GLEP is now purely technical specification. |
| 39 |
+ |
| 40 |
+ |
| 41 |
Motivation |
| 42 |
========== |
| 43 |
|
| 44 |
@@ -62,22 +70,6 @@ manager. |
| 45 |
Specification |
| 46 |
============= |
| 47 |
|
| 48 |
-Policy |
| 49 |
------- |
| 50 |
- |
| 51 |
-Following the acceptance of this GLEP, all new users and groups must |
| 52 |
-be created via user/group packages as defined in this GLEP. The old |
| 53 |
-method may still be used for existing users/groups, in existing |
| 54 |
-packages. |
| 55 |
- |
| 56 |
-All new users and groups must have unique UIDs/GIDs assigned |
| 57 |
-by developers. The developer adding them is responsible for checking |
| 58 |
-for collisions. |
| 59 |
- |
| 60 |
-Before adding a new user and/or group, the developer must send a RFC |
| 61 |
-to the ``gentoo-dev`` mailing list. |
| 62 |
- |
| 63 |
- |
| 64 |
Logical structure |
| 65 |
----------------- |
| 66 |
|
| 67 |
@@ -149,20 +141,6 @@ that. |
| 68 |
Rationale |
| 69 |
========= |
| 70 |
|
| 71 |
-Requiring mailing list RFC |
| 72 |
--------------------------- |
| 73 |
- |
| 74 |
-The policy explicitly requires RFCs for new users and groups, as they |
| 75 |
-have global scopes and effects of mistakes while adding them are hard |
| 76 |
-to fix. Wider review should decrease the risk of major design mistakes. |
| 77 |
- |
| 78 |
-To provide one example, right now we have two different packages |
| 79 |
-creating ``git`` user and requiring a different home directory for |
| 80 |
-the user. As a result, the first package being installed defines |
| 81 |
-the actual home directory, and both technically can not be installed |
| 82 |
-at the same time. |
| 83 |
- |
| 84 |
- |
| 85 |
Satisfied goals |
| 86 |
--------------- |
| 87 |
|
| 88 |
@@ -238,6 +216,6 @@ References |
| 89 |
|
| 90 |
Copyright |
| 91 |
========= |
| 92 |
-This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 |
| 93 |
+This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 |
| 94 |
Unported License. To view a copy of this license, visit |
| 95 |
-https://creativecommons.org/licenses/by-sa/3.0/. |
| 96 |
+https://creativecommons.org/licenses/by-sa/4.0/. |
| 97 |
-- |
| 98 |
2.24.0 |
Archives