/[gentoo]/xml/htdocs/proj/en/glep/glep-0019.txt
Gentoo

Diff of /xml/htdocs/proj/en/glep/glep-0019.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.1 Revision 1.6
1GLEP: 18 1GLEP: 19
2Title: Gentoo Bimonthly Publication 2Title: Gentoo Stable Portage Tree
3Version: $Revision: 1.1 $ 3Version: $Revision: 1.6 $
4Last-Modified: $Date: 2004/01/27 01:50:51 $ 4Last-Modified: $Date: 2004/11/02 15:38:58 $
5Author: Kurt Lieber <klieber@gentoo.org> 5Author: Kurt Lieber <klieber@gentoo.org>
6Status: Draft 6Status: Draft
7Type: Standards Track 7Type: Standards Track
8Content-Type: text/x-rst 8Content-Type: text/x-rst
9Created: 26-Jan-2004 9Created: 26-Jan-2004
10Post-History: 26-Jan-2004 10Post-History: 29-Jan-2004 2-Nov-2004
11 11
12 12
13Abstract 13Abstract
14======== 14========
15 15
20 20
21The proposed solution involves creating a separate tree in Portage that is 21The proposed solution involves creating a separate tree in Portage that is
22updated far less often than the regular tree. Outside of periodic updates, 22updated far less often than the regular tree. Outside of periodic updates,
23this tree would only be updated with critical bugfixes and security patches. 23this tree would only be updated with critical bugfixes and security patches.
24 24
25Status
26======
27
28Currently recruiting people who would be willing to help with this GLEP.
29
25Motivation 30Motivation
26========== 31==========
27 32
28Enterprise customers typically value stability and a predictable upgrade path 33Enterprise users typically value stability and a predictable upgrade path
29over having the latest packages or features available to them. Historically, 34over having the latest packages or features available to them. Historically,
30Gentoo Linux has been unable to provide such an environment due to the dynamic 35Gentoo Linux has been unable to provide such an environment due to the dynamic
31nature of the Portage tree. 36nature of the Portage tree.
32 37
33Specification 38Specification
69resource constrained and unable to meed future deadlines. 74resource constrained and unable to meed future deadlines.
70 75
71The suggestion that seemed to get the most traction was the creation of a new 76The suggestion that seemed to get the most traction was the creation of a new
72"stable" keyword which would be added to appropriate ebuilds. The use of 77"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 78"stable" would signify ebuilds that are ready for production in the stable
74tree whils "~stable" would be reserved for ebuilds which may be appropriate 79tree while "~stable" would be reserved for ebuilds which may be appropriate
75for the stable tree, but may require further testing before being deemed 80for 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 81"ready for production". Off-cycle bug fixes and/or security updates may be
77examples of ebuilds that require the ~server tag. 82examples of ebuilds that require the ~stable tag.
78 83
79Implementation 84Implementation
80============== 85==============
81 86
87While a 'stable' keyword was originally proposed, after further review, it was
88determined this offered no way to allow arch-specific stable ebuilds. As
89such, this GLEP proposes the use of 'stable:<arch>' and '~stable:<arch>'
90(stable:x86, stable:ppc, etc.)
91
82A new, stable tree will be created by scanning for the 'server' and '~server' 92A new, stable tree will be created by scanning for the 'stable:<arch>' and
83keywords in the ebuilds and pulling those ebuilds and associated files into a 93'~stable:<arch>' keywords in the ebuilds and pulling those ebuilds and
84separate branch of CVS. The stable tree should have the following features: 94associated files into a separate branch of CVS. The stable tree should have
95the following features:
85 96
86* Updated quarterly. Frozen during other times except for security/bug fixes 97* 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 98* 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 99 allows users to upgrade as infrequently as once per year without risking
100 the stable portage tree leaving them behind without an upgrade path.
89 101
90As mentioned above, the "stable" tree will be updated quarterly, ideally in 102As mentioned above, the "stable" tree will be updated quarterly, ideally in
91unison with the release schedule of the main Gentoo branch. This tree will be 103unison with the release schedule of the main Gentoo branch. This tree will be
92untouched outside of this update schedule except in the following cases: 104untouched outside of this update schedule except in the following cases:
93 105

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.6

  ViewVC Help
Powered by ViewVC 1.1.20