| 1 |
<?xml version="1.0" encoding="utf-8" ?>
|
| 2 |
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
| 3 |
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
| 4 |
<!--
|
| 5 |
This HTML is auto-generated. DO NOT EDIT THIS FILE! If you are writing a new
|
| 6 |
PEP, see http://www.python.org/peps/pep-0001.html for instructions and links
|
| 7 |
to templates. DO NOT USE THIS HTML FILE AS YOUR TEMPLATE!
|
| 8 |
-->
|
| 9 |
<head>
|
| 10 |
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
| 11 |
<meta name="generator" content="Docutils 0.3.3: http://docutils.sourceforge.net/" />
|
| 12 |
<title>GLEP 19 -- Gentoo Stable Portage Tree</title>
|
| 13 |
<link rel="stylesheet" href="tools/glep.css" type="text/css" />
|
| 14 |
</head>
|
| 15 |
<body bgcolor="white">
|
| 16 |
<table class="navigation" cellpadding="0" cellspacing="0"
|
| 17 |
width="100%" border="0">
|
| 18 |
<tr><td class="navicon" width="150" height="35">
|
| 19 |
<a href="http://www.gentoo.org/" title="Gentoo Linux Home Page">
|
| 20 |
<img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]"
|
| 21 |
border="0" width="150" height="35" /></a></td>
|
| 22 |
<td class="textlinks" align="left">
|
| 23 |
[<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>]
|
| 24 |
[<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>]
|
| 25 |
[<b><a href="./glep-0019.txt">GLEP Source</a></b>]
|
| 26 |
</td></tr></table>
|
| 27 |
<div class="document">
|
| 28 |
<table class="rfc2822 field-list" frame="void" rules="none">
|
| 29 |
<col class="field-name" />
|
| 30 |
<col class="field-body" />
|
| 31 |
<tbody valign="top">
|
| 32 |
<tr class="field"><th class="field-name">GLEP:</th><td class="field-body">19</td>
|
| 33 |
</tr>
|
| 34 |
<tr class="field"><th class="field-name">Title:</th><td class="field-body">Gentoo Stable Portage Tree</td>
|
| 35 |
</tr>
|
| 36 |
<tr class="field"><th class="field-name">Version:</th><td class="field-body">1.6</td>
|
| 37 |
</tr>
|
| 38 |
<tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/glep/glep-0019.txt">2004/11/02 15:38:58</a></td>
|
| 39 |
</tr>
|
| 40 |
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Kurt Lieber <klieber at gentoo.org></td>
|
| 41 |
</tr>
|
| 42 |
<tr class="field"><th class="field-name">Status:</th><td class="field-body">Draft</td>
|
| 43 |
</tr>
|
| 44 |
<tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td>
|
| 45 |
</tr>
|
| 46 |
<tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference" href="glep-0012.html">text/x-rst</a></td>
|
| 47 |
</tr>
|
| 48 |
<tr class="field"><th class="field-name">Created:</th><td class="field-body">26-Jan-2004</td>
|
| 49 |
</tr>
|
| 50 |
<tr class="field"><th class="field-name">Post-History:</th><td class="field-body">29-Jan-2004 2-Nov-2004</td>
|
| 51 |
</tr>
|
| 52 |
</tbody>
|
| 53 |
</table>
|
| 54 |
<hr />
|
| 55 |
<div class="contents topic" id="contents">
|
| 56 |
<p class="topic-title first"><a name="contents">Contents</a></p>
|
| 57 |
<ul class="simple">
|
| 58 |
<li><a class="reference" href="#abstract" id="id2" name="id2">Abstract</a></li>
|
| 59 |
<li><a class="reference" href="#status" id="id3" name="id3">Status</a></li>
|
| 60 |
<li><a class="reference" href="#motivation" id="id4" name="id4">Motivation</a></li>
|
| 61 |
<li><a class="reference" href="#specification" id="id5" name="id5">Specification</a></li>
|
| 62 |
<li><a class="reference" href="#rationale" id="id6" name="id6">Rationale</a></li>
|
| 63 |
<li><a class="reference" href="#implementation" id="id7" name="id7">Implementation</a></li>
|
| 64 |
<li><a class="reference" href="#backwards-compatibility" id="id8" name="id8">Backwards Compatibility</a></li>
|
| 65 |
<li><a class="reference" href="#copyright" id="id9" name="id9">Copyright</a></li>
|
| 66 |
</ul>
|
| 67 |
</div>
|
| 68 |
<div class="section" id="abstract">
|
| 69 |
<h1><a class="toc-backref" href="#id2" name="abstract">Abstract</a></h1>
|
| 70 |
<p>This GLEP is intended to propose a series of changes to the Portage tree that
|
| 71 |
are necessary to facilitate the use of Gentoo in areas where stability and
|
| 72 |
predictability are of paramount importance, including servers in enterprise
|
| 73 |
environments, mission critical workstations and other such installations.</p>
|
| 74 |
<p>The proposed solution involves creating a separate tree in Portage that is
|
| 75 |
updated far less often than the regular tree. Outside of periodic updates,
|
| 76 |
this tree would only be updated with critical bugfixes and security patches.</p>
|
| 77 |
</div>
|
| 78 |
<div class="section" id="status">
|
| 79 |
<h1><a class="toc-backref" href="#id3" name="status">Status</a></h1>
|
| 80 |
<p>Currently recruiting people who would be willing to help with this GLEP.</p>
|
| 81 |
</div>
|
| 82 |
<div class="section" id="motivation">
|
| 83 |
<h1><a class="toc-backref" href="#id4" name="motivation">Motivation</a></h1>
|
| 84 |
<p>Enterprise users typically value stability and a predictable upgrade path
|
| 85 |
over having the latest packages or features available to them. Historically,
|
| 86 |
Gentoo Linux has been unable to provide such an environment due to the dynamic
|
| 87 |
nature of the Portage tree.</p>
|
| 88 |
</div>
|
| 89 |
<div class="section" id="specification">
|
| 90 |
<h1><a class="toc-backref" href="#id5" name="specification">Specification</a></h1>
|
| 91 |
<p>The Gentoo Infrastructure team will need to provide an additional Portage tree
|
| 92 |
on our rsync mirroring system. This new tree will house the ebuilds
|
| 93 |
associated with the stable tree. It also impacts all Gentoo developers
|
| 94 |
responsible for creating and updating ebuilds as they will be expected to
|
| 95 |
integrate the tagging of ebuilds for the stable tree into their normal
|
| 96 |
development process, both for the quarterly release cycles as well as
|
| 97 |
off-cycle bug and security fixes.</p>
|
| 98 |
<p>The Gentoo Documentation team will also be affected as they will be
|
| 99 |
responsible for updating installation documents to take these new features
|
| 100 |
into account.</p>
|
| 101 |
</div>
|
| 102 |
<div class="section" id="rationale">
|
| 103 |
<h1><a class="toc-backref" href="#id6" name="rationale">Rationale</a></h1>
|
| 104 |
<p>A basic outline of various ways of adding a "stable" tree to Portage was
|
| 105 |
discussed in the gentoo managers meeting on 26-Jan-04. Consensus seemed to be
|
| 106 |
reached that such a solution was needed and that branching the gentoo-x86
|
| 107 |
repository was the appropriate way to accomplish this. The largest area of
|
| 108 |
disagreement surrounded how specific ebuilds should be targeted for inclusion
|
| 109 |
in the stable tree.</p>
|
| 110 |
<p>One suggested solution was a simple branch of the CVS tree and having
|
| 111 |
developers work in two separate branches; one for the stable tree and
|
| 112 |
another for the traditional tree. However, it was felt this would prove too
|
| 113 |
cumbersome in practice.</p>
|
| 114 |
<p>Another suggestion was to have a small group of dedicated gentoo-server
|
| 115 |
developers responsible for generating the contents of the stable tree, which
|
| 116 |
would provide more control and quality assurance over the ebuilds added to the
|
| 117 |
stable tree. While this might prove effective for a small number of ebuilds,
|
| 118 |
it is quite likely that this model would not scale enough to allow for a large
|
| 119 |
number of ebuilds in the stable tree and, over time, the project would become
|
| 120 |
resource constrained and unable to meed future deadlines.</p>
|
| 121 |
<p>The suggestion that seemed to get the most traction was the creation of a new
|
| 122 |
"stable" keyword which would be added to appropriate ebuilds. The use of
|
| 123 |
"stable" would signify ebuilds that are ready for production in the stable
|
| 124 |
tree while "~stable" would be reserved for ebuilds which may be appropriate
|
| 125 |
for the stable tree, but may require further testing before being deemed
|
| 126 |
"ready for production". Off-cycle bug fixes and/or security updates may be
|
| 127 |
examples of ebuilds that require the ~stable tag.</p>
|
| 128 |
</div>
|
| 129 |
<div class="section" id="implementation">
|
| 130 |
<h1><a class="toc-backref" href="#id7" name="implementation">Implementation</a></h1>
|
| 131 |
<p>While a 'stable' keyword was originally proposed, after further review, it was
|
| 132 |
determined this offered no way to allow arch-specific stable ebuilds. As
|
| 133 |
such, this GLEP proposes the use of 'stable:<arch>' and '~stable:<arch>'
|
| 134 |
(stable:x86, stable:ppc, etc.)</p>
|
| 135 |
<p>A new, stable tree will be created by scanning for the 'stable:<arch>' and
|
| 136 |
'~stable:<arch>' keywords in the ebuilds and pulling those ebuilds and
|
| 137 |
associated files into a separate branch of CVS. The stable tree should have
|
| 138 |
the following features:</p>
|
| 139 |
<ul class="simple">
|
| 140 |
<li>Updated quarterly. Frozen during other times except for security/bug fixes</li>
|
| 141 |
<li>All ebuilds should remain in the tree for a minimum of one year. This
|
| 142 |
allows users to upgrade as infrequently as once per year without risking
|
| 143 |
the stable portage tree leaving them behind without an upgrade path.</li>
|
| 144 |
</ul>
|
| 145 |
<p>As mentioned above, the "stable" tree will be updated quarterly, ideally in
|
| 146 |
unison with the release schedule of the main Gentoo branch. This tree will be
|
| 147 |
untouched outside of this update schedule except in the following cases:</p>
|
| 148 |
<ul class="simple">
|
| 149 |
<li>Security fixes and patches which result in a GLSA</li>
|
| 150 |
<li>Bug fixes for bugs ranked as 'maj' or above (may be overridden at the
|
| 151 |
discretion of the package maintainer.)</li>
|
| 152 |
</ul>
|
| 153 |
<p>In both cases, the maintainer of the package will be responsible for ensuring
|
| 154 |
these patches are properly committed to the stable tree out of cycle.</p>
|
| 155 |
</div>
|
| 156 |
<div class="section" id="backwards-compatibility">
|
| 157 |
<h1><a class="toc-backref" href="#id8" name="backwards-compatibility">Backwards Compatibility</a></h1>
|
| 158 |
<p>All features proposed here are new additions to existing processes and
|
| 159 |
features. There should be no impact on existing features and functionality.</p>
|
| 160 |
</div>
|
| 161 |
<div class="section" id="copyright">
|
| 162 |
<h1><a class="toc-backref" href="#id9" name="copyright">Copyright</a></h1>
|
| 163 |
<p>This document is licensed under the Creative Commons - Attribution / Share
|
| 164 |
Alike license. (<a class="reference" href="http://creativecommons.org/licenses/by-sa/1.0">http://creativecommons.org/licenses/by-sa/1.0</a>)</p>
|
| 165 |
</div>
|
| 166 |
</div>
|
| 167 |
|
| 168 |
<hr class="footer" />
|
| 169 |
<div class="footer">
|
| 170 |
<a class="reference" href="glep-0019.txt">View document source</a>.
|
| 171 |
Generated on: 2004-11-02 15:31 UTC.
|
| 172 |
Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source.
|
| 173 |
</div>
|
| 174 |
</body>
|
| 175 |
</html>
|
| 176 |
|
Parent Directory
| 
Revision Log
