--- xml/htdocs/proj/en/glep/glep-0003.html 2003/08/20 02:32:05 1.4 +++ xml/htdocs/proj/en/glep/glep-0003.html 2006/10/10 20:25:14 1.5 @@ -8,9 +8,252 @@ --> - + GLEP 3 -- Ebuild maintainter extension GLEP - + -
- +
@@ -33,9 +275,9 @@ - + - + @@ -52,8 +294,8 @@
Title:Ebuild maintainter extension GLEP
Version:1.1
Version:1.2
Last-Modified:2003/06/10 17:31:01
Last-Modified:2003/08/20 02:32:05
Author:Caleb Tennis <caleb at gentoo.org>

-
-

Contents

+
+

Contents

-
-

Abstract

+
+

Abstract

Gentoo's portage tree attempts to provide a self contained, easy to use, and automatic installation procedure for as many packages as can be maintained by developers.

@@ -78,15 +320,15 @@

This GLEP only applies to EBUILD based bugs that contain a request for a package to be committed or version bumped within portage.

-
-

Motivation

+
+

Motivation

As of the first draft of this GLEP, there are 1387 EBUILD bug requests in Gentoo's bugzilla database. Many of these requests contain ebuilds that have been submitted by the bug reporter and are simply awaiting a Gentoo developer to sponsor the submittal of the ebuild.

-
-

Rationale

+
+

Rationale

Gentoo's portage tree already contains the most popular ebuilds for packages available today. Many teams exist that are responsible for maintaining these core ebuilds in the portage tree. But, for ebuilds that are not as commonly @@ -100,12 +342,12 @@ make sure that all ebuilds have some person who is responsible for maintenance.

-
-

Backwards Compatibility

+
+

Backwards Compatibility

No current policies exist that interfere with this document.

-
-

Implementation

+
+

Implementation

Incoming ebuild bug reports should continue to be processed as normal.

Bug reports that do not contain an attached ebuild should be marked as NEEDINFO. A message asking the user to create and submit an ebuild should be @@ -124,8 +366,8 @@ that the ebuild is externally maintained, he/she can add that person to the CC list.

-
-

Security

+
+

Security

At the very least, all ebuilds must be looked over by the developer handling the commit.

In no case should a submitted digest file be used. The developer is @@ -135,15 +377,15 @@ handling the installation should take every step to ensure that no ebuild, package, or other files have been compromised.

-
-

Future

+
+

Future

Current proposals to rethink Gentoo portage and bug handling (a.k.a Herds) are still in negotiation. It is the intention of the author of this GLEP to evolve the concept of this GLEP as the Herds concept matures and stabilizes.

-
-

References

- +
[1]GLEP 2, Sample ReStructuredText GLEP Template, Goodyear, @@ -151,17 +393,18 @@
- - +