| 1 | GLEP: 19 |
1 | GLEP: 19 |
| 2 | Title: Gentoo Stable Portage Tree |
2 | Title: Gentoo Stable Portage Tree |
| 3 | Version: $Revision: 1.4 $ |
3 | Version: $Revision: 1.5 $ |
| 4 | Last-Modified: $Date: 2004/01/30 02:41:45 $ |
4 | Last-Modified: $Date: 2004/02/02 18:16:31 $ |
| 5 | Author: Kurt Lieber <klieber@gentoo.org> |
5 | Author: Kurt Lieber <klieber@gentoo.org> |
| 6 | Status: Draft |
6 | Status: Draft |
| 7 | Type: Standards Track |
7 | Type: Standards Track |
| 8 | Content-Type: text/x-rst |
8 | Content-Type: text/x-rst |
| 9 | Created: 26-Jan-2004 |
9 | Created: 26-Jan-2004 |
| … | |
… | |
| 23 | this tree would only be updated with critical bugfixes and security patches. |
23 | this tree would only be updated with critical bugfixes and security patches. |
| 24 | |
24 | |
| 25 | Motivation |
25 | Motivation |
| 26 | ========== |
26 | ========== |
| 27 | |
27 | |
| 28 | Enterprise customers typically value stability and a predictable upgrade path |
28 | Enterprise users typically value stability and a predictable upgrade path |
| 29 | over having the latest packages or features available to them. Historically, |
29 | over having the latest packages or features available to them. Historically, |
| 30 | Gentoo Linux has been unable to provide such an environment due to the dynamic |
30 | Gentoo Linux has been unable to provide such an environment due to the dynamic |
| 31 | nature of the Portage tree. |
31 | nature of the Portage tree. |
| 32 | |
32 | |
| 33 | Specification |
33 | Specification |
| … | |
… | |
| 72 | "stable" keyword which would be added to appropriate ebuilds. The use of |
72 | "stable" keyword which would be added to appropriate ebuilds. The use of |
| 73 | "stable" would signify ebuilds that are ready for production in the stable |
73 | "stable" would signify ebuilds that are ready for production in the stable |
| 74 | tree while "~stable" would be reserved for ebuilds which may be appropriate |
74 | tree while "~stable" would be reserved for ebuilds which may be appropriate |
| 75 | for the stable tree, but may require further testing before being deemed |
75 | for the stable tree, but may require further testing before being deemed |
| 76 | "ready for production". Off-cycle bug fixes and/or security updates may be |
76 | "ready for production". Off-cycle bug fixes and/or security updates may be |
| 77 | examples of ebuilds that require the ~server tag. |
77 | examples of ebuilds that require the ~stable tag. |
| 78 | |
78 | |
| 79 | Implementation |
79 | Implementation |
| 80 | ============== |
80 | ============== |
| 81 | |
81 | |
| 82 | While a 'stable' keyword was originally proposed, after further review, it was |
82 | While a 'stable' keyword was originally proposed, after further review, it was |
Parent Directory
| 
Revision Log
| 
Patch