| 1 | GLEP: 40 |
1 | GLEP: 40 |
| 2 | Title: Standardizing "arch" keywording across all archs. |
2 | Title: Standardizing "arch" keywording across all archs. |
| 3 | Version: $Revision: 1.2 $ |
3 | Version: $Revision: 1.3 $ |
| 4 | Last-Modified: $Date: 2005/09/15 21:02:11 $ |
4 | Last-Modified: $Date: 2005/11/13 17:16:50 $ |
| 5 | Author: Grant Goodyear <g2boojum@gentoo.org> |
5 | Author: Grant Goodyear <g2boojum@gentoo.org> |
| 6 | Status: Approved |
6 | Status: Approved |
| 7 | Type: Standards Track |
7 | Type: Standards Track |
| 8 | Content-Type: text/x-rst |
8 | Content-Type: text/x-rst |
| 9 | Created: 3-Sep-2005 |
9 | Created: 3-Sep-2005 |
| … | |
… | |
| 84 | |
84 | |
| 85 | Rationale |
85 | Rationale |
| 86 | ========= |
86 | ========= |
| 87 | |
87 | |
| 88 | There will be a considerable one-time cost involved in establishing a robust |
88 | There will be a considerable one-time cost involved in establishing a robust |
| 89 | x86 arch team--a good number of bodies (the amd64 atch team has 19 active devs |
89 | x86 arch team--a good number of bodies (the amd64 arch team has 19 active devs |
| 90 | and 12 active non-dev arch testers) need to be recruited to be part of the |
90 | and 12 active non-dev arch testers) need to be recruited to be part of the |
| 91 | new arch team, and convincing devs that it is in their best interests to work |
91 | new arch team, and convincing devs that it is in their best interests to work |
| 92 | in a new fashion is likely to be even harder. Certainly the benefit of |
92 | in a new fashion is likely to be even harder. Certainly the benefit of |
| 93 | consistency between the various archs is obvious, but is it worth the cost |
93 | consistency between the various archs is obvious, but is it worth the cost |
| 94 | involved? Here are the arguments for enduring the pain involved: |
94 | involved? Here are the arguments for enduring the pain involved: |