| 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 |
Currently recruiting people who would be willing to help with this GLEP.
+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.
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.
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.
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.
All features proposed here are new additions to existing processes and features. There should be no impact on existing features and functionality.
This document is licensed under the Creative Commons - Attribution / Share Alike license. (http://creativecommons.org/licenses/by-sa/1.0)