| 1 | GLEP: 18 |
1 | GLEP: 19 |
| 2 | Title: Gentoo Bimonthly Publication |
2 | Title: Gentoo Stable Portage Tree |
| 3 | Version: $Revision: 1.1 $ |
3 | Version: $Revision: 1.3 $ |
| 4 | Last-Modified: $Date: 2004/01/27 01:50:51 $ |
4 | Last-Modified: $Date: 2004/01/30 02:27:28 $ |
| 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 |
| … | |
… | |
| 77 | examples of ebuilds that require the ~server tag. |
77 | examples of ebuilds that require the ~server tag. |
| 78 | |
78 | |
| 79 | Implementation |
79 | Implementation |
| 80 | ============== |
80 | ============== |
| 81 | |
81 | |
|
|
82 | While a 'stable' keyword was originally proposed, after further review, it was |
|
|
83 | determined this offered no way to allow arch-specific stable ebuilds. As |
|
|
84 | such, this GLEP proposes the use of 'stable:<arch>' and '~stable:<arch>' |
|
|
85 | (stable:x86, stable:ppc, etc.) |
|
|
86 | |
| 82 | A new, stable tree will be created by scanning for the 'server' and '~server' |
87 | A new, stable tree will be created by scanning for the 'stable:<arch>' and |
| 83 | keywords in the ebuilds and pulling those ebuilds and associated files into a |
88 | '~stable:<arch>' keywords in the ebuilds and pulling those ebuilds and |
| 84 | separate branch of CVS. The stable tree should have the following features: |
89 | associated files into a separate branch of CVS. The stable tree should have |
|
|
90 | the following features: |
| 85 | |
91 | |
| 86 | * Updated quarterly. Frozen during other times except for security/bug fixes |
92 | * Updated quarterly. Frozen during other times except for security/bug fixes |
| 87 | * All ebuilds should remain in the tree for a minimum of one year to ensure |
93 | * All ebuilds should remain in the tree for a minimum of one year. This |
| 88 | that administrators will know how often their servers need to be upgraded |
94 | allows users to upgrade as infrequently as once per year without risking |
|
|
95 | the stable portage tree leaving them behind without an upgrade path. |
| 89 | |
96 | |
| 90 | As mentioned above, the "stable" tree will be updated quarterly, ideally in |
97 | As mentioned above, the "stable" tree will be updated quarterly, ideally in |
| 91 | unison with the release schedule of the main Gentoo branch. This tree will be |
98 | unison with the release schedule of the main Gentoo branch. This tree will be |
| 92 | untouched outside of this update schedule except in the following cases: |
99 | untouched outside of this update schedule except in the following cases: |
| 93 | |
100 | |
Parent Directory
| 
Revision Log
| 
Patch