--- xml/htdocs/proj/en/glep/glep-0040.html 2005/09/09 03:08:59 1.1 +++ xml/htdocs/proj/en/glep/glep-0040.html 2005/09/15 21:04:13 1.2 @@ -32,13 +32,13 @@ Title:Standardizing "arch" keywording across all archs. -Version:1.1 +Version:1.2 -Last-Modified:2005/09/09 03:06:28 +Last-Modified:2005/09/15 21:02:11 Author:Grant Goodyear <g2boojum at gentoo.org> -Status:Draft +Status:Approved Type:Standards Track @@ -46,7 +46,7 @@ Created:3-Sep-2005 -Post-History:6-Sep-2005 +Post-History:6-Sep-2005 15-Sep-2005 @@ -54,37 +54,42 @@

Contents

+
+

Status

+

Approved by the Gentoo Council on 15 September 2005.

+
-

Credits

+

Credits

This GLEP originated from a rather contentious discussion [1] on gentoo-dev about combining the x86 and amd64 keywords. This GLEP attempts to get at the heart of that discontent. The proposed stable-keyword guidelines have been lifted verbatim from The Doc [2].

-

Abstract

+

Abstract

It is time for x86 to no longer be an exception to the standard keywording guidelines. Thus, an x86 arch team should be responsible for moving packages from ~x86 to x86.

-

Motivation

+

Motivation

The original, informal x86 keywording policy, where almost any x86 dev (which were the vast majority of devs) who used a package could mark it stable, arose from a time when there were relatively few Gentoo devs. Adding packages to @@ -102,9 +107,9 @@ benefit x86 as well.

-

Specification

+

Specification

-

Stabling guidelines for all archs

+

Stabling guidelines for all archs

For a package to move to stable, the following guidelines must be met:

-

x86 arch team

+

x86 arch team

A robust x86 arch team needs to be created. The x86@gentoo.org alias already exists, and it merely needs to be used. This team, with the aid of potential non-dev arch testers, has the responsibility of stabling all x86 packages. @@ -130,7 +135,7 @@

-

Rationale

+

Rationale

There will be a considerable one-time cost involved in establishing a robust x86 arch team--a good number of bodies (the amd64 atch team has 19 active devs and 12 active non-dev arch testers) need to be recruited to be part of the @@ -158,13 +163,13 @@

-

Implementation

+

Implementation

Creation of a robust x86 team is already underway. The more vital step is the official change in policy, along with a sustained effort to get existing x86 devs to go along with it.

-

Alternative Ideas

+

Alternative Ideas

Stuart [4] has suggested the creation of a new arch keyword: "[-]maint", which would exist in tandem with the normal arch keywords, thereby making the package maintainer's intention explicit. Ciaranm has responded that by @@ -185,11 +190,11 @@ the support burden for that package.

-

Backwards Compatibility

+

Backwards Compatibility

Not really an issue here.

-

References

+

References

@@ -216,7 +221,7 @@
@@ -224,7 +229,7 @@