--- xml/htdocs/proj/en/glep/glep-0019.html 2004/02/02 18:16:31 1.2 +++ xml/htdocs/proj/en/glep/glep-0019.html 2004/11/02 15:39:07 1.3 @@ -8,7 +8,7 @@ --> - + GLEP 19 -- Gentoo Stable Portage Tree @@ -22,7 +22,7 @@ [Gentoo Linux Home] [GLEP Index] -[GLEP Source] +[GLEP Source]
@@ -33,9 +33,9 @@ - + - + @@ -43,25 +43,26 @@ - + - +
Title:Gentoo Stable Portage Tree
Version:1.4
Version:1.6
Last-Modified:2004/01/30 02:41:45
Last-Modified:2004/11/02 15:38:58
Author:Kurt Lieber <klieber at gentoo.org>
Type:Standards Track
Content-Type:text/x-rst
Content-Type:text/x-rst
Created:26-Jan-2004
Post-History:29-Jan-2004
Post-History:29-Jan-2004 2-Nov-2004

-

Contents

+

Contents

@@ -74,15 +75,19 @@ updated far less often than the regular tree. Outside of periodic updates, this tree would only be updated with critical bugfixes and security patches.

+
+

Status

+

Currently recruiting people who would be willing to help with this GLEP.

+
-

Motivation

+

Motivation

Enterprise users typically value stability and a predictable upgrade path over having the latest packages or features available to them. Historically, Gentoo Linux has been unable to provide such an environment due to the dynamic nature of the Portage tree.

-

Specification

+

Specification

The Gentoo Infrastructure team will need to provide an additional Portage tree on our rsync mirroring system. This new tree will house the ebuilds associated with the stable tree. It also impacts all Gentoo developers @@ -95,7 +100,7 @@ into account.

-

Rationale

+

Rationale

A basic outline of various ways of adding a "stable" tree to Portage was discussed in the gentoo managers meeting on 26-Jan-04. Consensus seemed to be reached that such a solution was needed and that branching the gentoo-x86 @@ -122,7 +127,7 @@ examples of ebuilds that require the ~stable tag.

-

Implementation

+

Implementation

While a 'stable' keyword was originally proposed, after further review, it was determined this offered no way to allow arch-specific stable ebuilds. As such, this GLEP proposes the use of 'stable:<arch>' and '~stable:<arch>' @@ -149,21 +154,21 @@ these patches are properly committed to the stable tree out of cycle.

-

Backwards Compatibility

+

Backwards Compatibility

All features proposed here are new additions to existing processes and features. There should be no impact on existing features and functionality.

- +