| 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 |
<head>
|
| 6 |
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
| 7 |
<meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" />
|
| 8 |
<title>GLEP 19 -- Gentoo Stable Portage Tree</title>
|
| 9 |
<link rel="stylesheet" href="tools/glep.css" type="text/css" />
|
| 10 |
</head>
|
| 11 |
<body bgcolor="white">
|
| 12 |
<table class="navigation" cellpadding="0" cellspacing="0"
|
| 13 |
width="100%" border="0">
|
| 14 |
<tr><td class="navicon" width="150" height="35">
|
| 15 |
<a href="http://www.gentoo.org/" title="Gentoo Linux Home Page">
|
| 16 |
<img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]"
|
| 17 |
border="0" width="150" height="35" /></a></td>
|
| 18 |
<td class="textlinks" align="left">
|
| 19 |
[<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>]
|
| 20 |
[<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>]
|
| 21 |
[<b><a href="http://www.gentoo.org/proj/en/glep/glep-0019.txt">GLEP Source</a></b>]
|
| 22 |
</td></tr></table>
|
| 23 |
<table class="rfc2822 docutils field-list" frame="void" rules="none">
|
| 24 |
<col class="field-name" />
|
| 25 |
<col class="field-body" />
|
| 26 |
<tbody valign="top">
|
| 27 |
<tr class="field"><th class="field-name">GLEP:</th><td class="field-body">19</td>
|
| 28 |
</tr>
|
| 29 |
<tr class="field"><th class="field-name">Title:</th><td class="field-body">Gentoo Stable Portage Tree</td>
|
| 30 |
</tr>
|
| 31 |
<tr class="field"><th class="field-name">Version:</th><td class="field-body">1.8</td>
|
| 32 |
</tr>
|
| 33 |
<tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/proj/en/glep/glep-0019.txt?cvsroot=gentoo">2006/10/10 16:54:34</a></td>
|
| 34 |
</tr>
|
| 35 |
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Kurt Lieber <klieber at gentoo.org></td>
|
| 36 |
</tr>
|
| 37 |
<tr class="field"><th class="field-name">Status:</th><td class="field-body">Withdrawn</td>
|
| 38 |
</tr>
|
| 39 |
<tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td>
|
| 40 |
</tr>
|
| 41 |
<tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference" href="glep-0002.html">text/x-rst</a></td>
|
| 42 |
</tr>
|
| 43 |
<tr class="field"><th class="field-name">Created:</th><td class="field-body">26-Jan-2004</td>
|
| 44 |
</tr>
|
| 45 |
<tr class="field"><th class="field-name">Post-History:</th><td class="field-body">29-Jan-2004 2-Nov-2004 7-Dec-2004 10-Oct-2006</td>
|
| 46 |
</tr>
|
| 47 |
</tbody>
|
| 48 |
</table>
|
| 49 |
<hr />
|
| 50 |
<div class="contents topic">
|
| 51 |
<p class="topic-title first"><a id="contents" name="contents">Contents</a></p>
|
| 52 |
<ul class="simple">
|
| 53 |
<li><a class="reference" href="#status" id="id3" name="id3">Status</a></li>
|
| 54 |
<li><a class="reference" href="#abstract" id="id4" name="id4">Abstract</a></li>
|
| 55 |
<li><a class="reference" href="#id1" id="id5" name="id5">Status</a></li>
|
| 56 |
<li><a class="reference" href="#motivation" id="id6" name="id6">Motivation</a></li>
|
| 57 |
<li><a class="reference" href="#specification" id="id7" name="id7">Specification</a></li>
|
| 58 |
<li><a class="reference" href="#rationale" id="id8" name="id8">Rationale</a></li>
|
| 59 |
<li><a class="reference" href="#implementation" id="id9" name="id9">Implementation</a></li>
|
| 60 |
<li><a class="reference" href="#backwards-compatibility" id="id10" name="id10">Backwards Compatibility</a></li>
|
| 61 |
<li><a class="reference" href="#copyright" id="id11" name="id11">Copyright</a></li>
|
| 62 |
</ul>
|
| 63 |
</div>
|
| 64 |
<div class="section">
|
| 65 |
<h1><a class="toc-backref" href="#id3" id="status" name="status">Status</a></h1>
|
| 66 |
<p>Withdrawn by the author. "If someone wants to take up the torch, more
|
| 67 |
power to them, but they should probably start clean with a new glep."</p>
|
| 68 |
</div>
|
| 69 |
<div class="section">
|
| 70 |
<h1><a class="toc-backref" href="#id4" id="abstract" name="abstract">Abstract</a></h1>
|
| 71 |
<p>This GLEP is intended to propose a series of changes to the Portage tree that
|
| 72 |
are necessary to facilitate the use of Gentoo in areas where stability and
|
| 73 |
predictability are of paramount importance, including servers in enterprise
|
| 74 |
environments, mission critical workstations and other such installations.</p>
|
| 75 |
<p>The proposed solution involves creating a separate tree in Portage that is
|
| 76 |
updated far less often than the regular tree. Outside of periodic updates,
|
| 77 |
this tree would only be updated with critical bugfixes and security patches.</p>
|
| 78 |
</div>
|
| 79 |
<div class="section">
|
| 80 |
<h1><a class="toc-backref" href="#id5" id="id1" name="id1">Status</a></h1>
|
| 81 |
<p>Currently recruiting people who would be willing to help with this GLEP.</p>
|
| 82 |
</div>
|
| 83 |
<div class="section">
|
| 84 |
<h1><a class="toc-backref" href="#id6" id="motivation" name="motivation">Motivation</a></h1>
|
| 85 |
<p>Enterprise users typically value stability and a predictable upgrade path
|
| 86 |
over having the latest packages or features available to them. Historically,
|
| 87 |
Gentoo Linux has been unable to provide such an environment due to the dynamic
|
| 88 |
nature of the Portage tree.</p>
|
| 89 |
</div>
|
| 90 |
<div class="section">
|
| 91 |
<h1><a class="toc-backref" href="#id7" id="specification" name="specification">Specification</a></h1>
|
| 92 |
<p>The Gentoo Infrastructure team will need to provide an additional Portage tree
|
| 93 |
on our rsync mirroring system. This new tree will house the ebuilds
|
| 94 |
associated with the stable tree. It also impacts all Gentoo developers
|
| 95 |
responsible for creating and updating ebuilds as they will be expected to
|
| 96 |
integrate the tagging of ebuilds for the stable tree into their normal
|
| 97 |
development process, both for the quarterly release cycles as well as
|
| 98 |
off-cycle bug and security fixes.</p>
|
| 99 |
<p>The Gentoo Documentation team will also be affected as they will be
|
| 100 |
responsible for updating installation documents to take these new features
|
| 101 |
into account.</p>
|
| 102 |
</div>
|
| 103 |
<div class="section">
|
| 104 |
<h1><a class="toc-backref" href="#id8" id="rationale" name="rationale">Rationale</a></h1>
|
| 105 |
<p>A basic outline of various ways of adding a "stable" tree to Portage was
|
| 106 |
discussed in the gentoo managers meeting on 26-Jan-04. Consensus seemed to be
|
| 107 |
reached that such a solution was needed and that branching the gentoo-x86
|
| 108 |
repository was the appropriate way to accomplish this. The largest area of
|
| 109 |
disagreement surrounded how specific ebuilds should be targeted for inclusion
|
| 110 |
in the stable tree.</p>
|
| 111 |
<p>One suggested solution was a simple branch of the CVS tree and having
|
| 112 |
developers work in two separate branches; one for the stable tree and
|
| 113 |
another for the traditional tree. However, it was felt this would prove too
|
| 114 |
cumbersome in practice.</p>
|
| 115 |
<p>Another suggestion was to have a small group of dedicated gentoo-server
|
| 116 |
developers responsible for generating the contents of the stable tree, which
|
| 117 |
would provide more control and quality assurance over the ebuilds added to the
|
| 118 |
stable tree. While this might prove effective for a small number of ebuilds,
|
| 119 |
it is quite likely that this model would not scale enough to allow for a large
|
| 120 |
number of ebuilds in the stable tree and, over time, the project would become
|
| 121 |
resource constrained and unable to meed future deadlines.</p>
|
| 122 |
<p>While the original draft of this GLEP called for the creation of a stable
|
| 123 |
keyword, we have since discarded that idea in favor of creating a custom
|
| 124 |
profile, which will be used to track a subset of packages and versions.</p>
|
| 125 |
</div>
|
| 126 |
<div class="section">
|
| 127 |
<h1><a class="toc-backref" href="#id9" id="implementation" name="implementation">Implementation</a></h1>
|
| 128 |
<p>This GLEP will create a new set of cascaded profiles (one per release, not to
|
| 129 |
exceed two per year) which will contain a subset of packages, including
|
| 130 |
versions. This profile will "pin" a Gentoo Linux box to a specific set of
|
| 131 |
packages and will only be updated for security updates and, in rare
|
| 132 |
circumstances, major bug fixes.</p>
|
| 133 |
<p>Because this profile will be cascaded, the option exists for other developers
|
| 134 |
to create their own profile, containing a subset of packages not found in the
|
| 135 |
"main" stable tree and include those as part of the overall stable profile.
|
| 136 |
These cases will be treated on a one-off basis.</p>
|
| 137 |
<p>The initial version will be x86 only, though other people will be encouraged
|
| 138 |
to provide separate stable profiles for other arches. It is expected that any
|
| 139 |
effort to provide a stable tree for any arch or flavor of Gentoo will follow
|
| 140 |
the basic outline of this GLEP to ensure consistency for our users.</p>
|
| 141 |
<p>In addition to a custom profile, this GLEP will also create a separate rsync
|
| 142 |
repository, "gentoo-stable-portage", which will be available on all servers in
|
| 143 |
the rsync.gentoo.org rotation. This repository will be <em>identical</em> to the
|
| 144 |
main gentoo-portage repository except that the --delete flag will be removed
|
| 145 |
from the rsync option that populates the tree. This will ensure that users of
|
| 146 |
the stable profile will not have to worry about ebuilds for their packages
|
| 147 |
disappearing.</p>
|
| 148 |
<p>Stable profiles will be maintained on an N - 2 basis. That is to say that we
|
| 149 |
will maintain a stable profile for the most current release, plus the previous
|
| 150 |
two releases. With the expected release schedule for 2005, this will result
|
| 151 |
in each profile being supported for approximately 18 months. Future versions
|
| 152 |
of the stable portage tree may seek to increase the life of these profiles.</p>
|
| 153 |
</div>
|
| 154 |
<div class="section">
|
| 155 |
<h1><a class="toc-backref" href="#id10" id="backwards-compatibility" name="backwards-compatibility">Backwards Compatibility</a></h1>
|
| 156 |
<p>All features proposed here are new additions to existing processes and
|
| 157 |
features. There should be no impact on existing features and functionality.</p>
|
| 158 |
</div>
|
| 159 |
<div class="section">
|
| 160 |
<h1><a class="toc-backref" href="#id11" id="copyright" name="copyright">Copyright</a></h1>
|
| 161 |
<p>This document is licensed under the Creative Commons - Attribution / Share
|
| 162 |
Alike license. (<a class="reference" href="http://creativecommons.org/licenses/by-sa/1.0">http://creativecommons.org/licenses/by-sa/1.0</a>)</p>
|
| 163 |
</div>
|
| 164 |
|
| 165 |
</div>
|
| 166 |
<div class="footer">
|
| 167 |
<hr class="footer" />
|
| 168 |
<a class="reference" href="glep-0019.txt">View document source</a>.
|
| 169 |
Generated on: 2007-10-13 13:39 UTC.
|
| 170 |
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.
|
| 171 |
|
| 172 |
</div>
|
| 173 |
</body>
|
| 174 |
</html>
|
| 175 |
|
Parent Directory
| 
Revision Log
