| 1 |
antarus 08/01/06 02:09:00 |
| 2 |
|
| 3 |
Modified: glep-0054.html glep-0054.txt |
| 4 |
Log: |
| 5 |
Editor Stamp of Coolness on glep54, redid HTML with minor changes which were sent to the author prior being commited. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.7 xml/htdocs/proj/en/glep/glep-0054.html |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/glep/glep-0054.html?rev=1.7&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/glep/glep-0054.html?rev=1.7&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/glep/glep-0054.html?r1=1.6&r2=1.7 |
| 13 |
|
| 14 |
Index: glep-0054.html |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/glep/glep-0054.html,v |
| 17 |
retrieving revision 1.6 |
| 18 |
retrieving revision 1.7 |
| 19 |
diff -u -r1.6 -r1.7 |
| 20 |
--- glep-0054.html 17 Dec 2007 21:10:03 -0000 1.6 |
| 21 |
+++ glep-0054.html 6 Jan 2008 02:08:59 -0000 1.7 |
| 22 |
@@ -1,11 +1,7 @@ |
| 23 |
<?xml version="1.0" encoding="utf-8" ?> |
| 24 |
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| 25 |
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> |
| 26 |
-<!-- |
| 27 |
-This HTML is auto-generated. DO NOT EDIT THIS FILE! If you are writing a new |
| 28 |
-PEP, see http://www.python.org/peps/pep-0001.html for instructions and links |
| 29 |
-to templates. DO NOT USE THIS HTML FILE AS YOUR TEMPLATE! |
| 30 |
---> |
| 31 |
+ |
| 32 |
<head> |
| 33 |
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> |
| 34 |
<meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" /> |
| 35 |
@@ -21,7 +17,7 @@ |
| 36 |
border="0" width="150" height="35" /></a></td> |
| 37 |
<td class="textlinks" align="left"> |
| 38 |
[<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>] |
| 39 |
-[<b><a href="http://www.gentoo.org/peps">GLEP Index</a></b>] |
| 40 |
+[<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>] |
| 41 |
[<b><a href="http://www.gentoo.org/proj/en/glep/glep-0054.txt">GLEP Source</a></b>] |
| 42 |
</td></tr></table> |
| 43 |
<table class="rfc2822 docutils field-list" frame="void" rules="none"> |
| 44 |
@@ -69,18 +65,18 @@ |
| 45 |
</div> |
| 46 |
<div class="section"> |
| 47 |
<h1><a class="toc-backref" href="#id3" id="motivation" name="motivation">Motivation</a></h1> |
| 48 |
-<p>Currently there is no standard way of marking SCM ebuilds. Using 9999 as the |
| 49 |
+<p>Currently there is no standard way of identifying SCM ebuilds. Using 9999 as the |
| 50 |
version is pretty common, but it is handled like any other ebuild and hence |
| 51 |
portage cannot provide any additional features for packages with such a version. |
| 52 |
-Another way is adding separate package with -cvs suffix in its name, but that |
| 53 |
-forces to use <tt class="docutils literal"><span class="pre">||</span> <span class="pre">(</span> <span class="pre">cat/pkg</span> <span class="pre">cat/pkg-cvs</span> <span class="pre">)</span></tt> dependencies. The closest to what |
| 54 |
-is proposed in this GLEP is the <tt class="docutils literal"><span class="pre">cvs</span></tt> version part, but its implementation is |
| 55 |
-of very limited use. It has strange comparison rules, no documentation, has |
| 56 |
-never been used in the tree and has a misleading name.</p> |
| 57 |
+Another way is adding a separate package with a -cvs suffix in its name, but |
| 58 |
+that forces the author to use <tt class="docutils literal"><span class="pre">||</span> <span class="pre">(</span> <span class="pre">cat/pkg</span> <span class="pre">cat/pkg-cvs</span> <span class="pre">)</span></tt> dependencies. The |
| 59 |
+closest to what is proposed in this GLEP is the <tt class="docutils literal"><span class="pre">cvs</span></tt> version part, but its |
| 60 |
+implementation is of very limited use. It has strange comparison rules, no |
| 61 |
+documentation, has been used sparingly (if ever) and has a misleading name.</p> |
| 62 |
<p>The possibility for package managers to recognise SCM ebuilds would allow them |
| 63 |
to add features dedicated specially to said ebuilds. One such feature could be |
| 64 |
-automatic re-installation of SCM packages once a day or week, but that's beyond |
| 65 |
-this GLEP.</p> |
| 66 |
+automatic re-installation of SCM packages once a day or week. Any |
| 67 |
+specifications for such features are beyond the scope of this GLEP.</p> |
| 68 |
</div> |
| 69 |
<div class="section"> |
| 70 |
<h1><a class="toc-backref" href="#id4" id="specification" name="specification">Specification</a></h1> |
| 71 |
@@ -105,11 +101,16 @@ |
| 72 |
<blockquote> |
| 73 |
<ul class="simple"> |
| 74 |
<li>When comparing version components from left to right the scm component has the |
| 75 |
-highest priority.</li> |
| 76 |
+highest priority over other version components. Hence |
| 77 |
+<tt class="docutils literal"><span class="pre">pkg-1_alpha-r3</span> <span class="pre"><</span> <span class="pre">pkg-1-scm</span></tt>, 'scm' is greater than 'alpha-r3'.</li> |
| 78 |
<li>Current suffixes with no number part no longer default to zero if they are |
| 79 |
followed by an scm suffix. If that's the case the number part is considered |
| 80 |
to be of a maximum value. Hence <tt class="docutils literal"><span class="pre">1_alpha2-scm</span> <span class="pre"><</span> <span class="pre">1_alpha-scm</span></tt>, but still |
| 81 |
-<tt class="docutils literal"><span class="pre">1_alpha</span> <span class="pre">==</span> <span class="pre">1_alpha0</span></tt>.</li> |
| 82 |
+<tt class="docutils literal"><span class="pre">1_alpha</span> <span class="pre">==</span> <span class="pre">1_alpha0</span></tt>. The rationale behind this choice is to allow |
| 83 |
+multiple branches. For instance imagine a package with an alpha branch |
| 84 |
+and multiple scm releases, as the following: <tt class="docutils literal"><span class="pre">alpha-scm</span></tt>, |
| 85 |
+<tt class="docutils literal"><span class="pre">alpha2-scm</span></tt>, <tt class="docutils literal"><span class="pre">alpha3-scm</span></tt> and so forth. The desired outcome is |
| 86 |
+for <tt class="docutils literal"><span class="pre">alpha-scm</span></tt> to be greater than all other branches of the same tree.</li> |
| 87 |
</ul> |
| 88 |
</blockquote> |
| 89 |
<p>Example parsing:</p> |
| 90 |
@@ -184,7 +185,7 @@ |
| 91 |
<div class="footer"> |
| 92 |
<hr class="footer" /> |
| 93 |
<a class="reference" href="glep-0054.txt">View document source</a>. |
| 94 |
-Generated on: 2007-12-17 21:09 UTC. |
| 95 |
+Generated on: 2008-01-06 02:08 UTC. |
| 96 |
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. |
| 97 |
|
| 98 |
</div> |
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
1.5 xml/htdocs/proj/en/glep/glep-0054.txt |
| 103 |
|
| 104 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/glep/glep-0054.txt?rev=1.5&view=markup |
| 105 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/glep/glep-0054.txt?rev=1.5&content-type=text/plain |
| 106 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/glep/glep-0054.txt?r1=1.4&r2=1.5 |
| 107 |
|
| 108 |
Index: glep-0054.txt |
| 109 |
=================================================================== |
| 110 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/glep/glep-0054.txt,v |
| 111 |
retrieving revision 1.4 |
| 112 |
retrieving revision 1.5 |
| 113 |
diff -u -r1.4 -r1.5 |
| 114 |
--- glep-0054.txt 17 Dec 2007 18:42:33 -0000 1.4 |
| 115 |
+++ glep-0054.txt 6 Jan 2008 02:08:59 -0000 1.5 |
| 116 |
@@ -1,7 +1,7 @@ |
| 117 |
GLEP: 54 |
| 118 |
Title: scm package version suffix |
| 119 |
-Version: $Revision: 1.4 $ |
| 120 |
-Last-Modified: $Date: 2007/12/17 18:42:33 $ |
| 121 |
+Version: $Revision: 1.5 $ |
| 122 |
+Last-Modified: $Date: 2008/01/06 02:08:59 $ |
| 123 |
Author: Piotr Jaroszyński <peper@g.o> |
| 124 |
Status: Draft |
| 125 |
Type: Standards Track |
| 126 |
@@ -18,23 +18,24 @@ |
| 127 |
Motivation |
| 128 |
========== |
| 129 |
|
| 130 |
-Currently there is no standard way of marking SCM ebuilds. Using 9999 as the |
| 131 |
+Currently there is no standard way of identifying SCM ebuilds. Using 9999 as the |
| 132 |
version is pretty common, but it is handled like any other ebuild and hence |
| 133 |
portage cannot provide any additional features for packages with such a version. |
| 134 |
-Another way is adding separate package with -cvs suffix in its name, but that |
| 135 |
-forces to use ``|| ( cat/pkg cat/pkg-cvs )`` dependencies. The closest to what |
| 136 |
-is proposed in this GLEP is the ``cvs`` version part, but its implementation is |
| 137 |
-of very limited use. It has strange comparison rules, no documentation, has |
| 138 |
-never been used in the tree and has a misleading name. |
| 139 |
+Another way is adding a separate package with a -cvs suffix in its name, but |
| 140 |
+that forces the author to use ``|| ( cat/pkg cat/pkg-cvs )`` dependencies. The |
| 141 |
+closest to what is proposed in this GLEP is the ``cvs`` version part, but its |
| 142 |
+implementation is of very limited use. It has strange comparison rules, no |
| 143 |
+documentation, has been used sparingly (if ever) and has a misleading name. |
| 144 |
|
| 145 |
The possibility for package managers to recognise SCM ebuilds would allow them |
| 146 |
to add features dedicated specially to said ebuilds. One such feature could be |
| 147 |
-automatic re-installation of SCM packages once a day or week, but that's beyond |
| 148 |
-this GLEP. |
| 149 |
+automatic re-installation of SCM packages once a day or week. Any |
| 150 |
+specifications for such features are beyond the scope of this GLEP. |
| 151 |
|
| 152 |
Specification |
| 153 |
============= |
| 154 |
|
| 155 |
+ |
| 156 |
``scm`` is a special suffix. It can be used on its own, but also in any other |
| 157 |
valid version spec, just before the place where revision would go. And just like |
| 158 |
revision it can be used only once in a version spec, e.g.: |
| 159 |
@@ -54,11 +55,16 @@ |
| 160 |
The addition of the scm suffix yields changes in version comparison: |
| 161 |
|
| 162 |
* When comparing version components from left to right the scm component has the |
| 163 |
- highest priority. |
| 164 |
+ highest priority over other version components. Hence |
| 165 |
+ ``pkg-1_alpha-r3 < pkg-1-scm``, 'scm' is greater than 'alpha-r3'. |
| 166 |
* Current suffixes with no number part no longer default to zero if they are |
| 167 |
followed by an scm suffix. If that's the case the number part is considered |
| 168 |
to be of a maximum value. Hence ``1_alpha2-scm < 1_alpha-scm``, but still |
| 169 |
- ``1_alpha == 1_alpha0``. |
| 170 |
+ ``1_alpha == 1_alpha0``. The rationale behind this choice is to allow |
| 171 |
+ multiple branches. For instance imagine a package with an alpha branch |
| 172 |
+ and multiple scm releases, as the following: ``alpha-scm``, |
| 173 |
+ ``alpha2-scm``, ``alpha3-scm`` and so forth. The desired outcome is |
| 174 |
+ for ``alpha-scm`` to be greater than all other branches of the same tree. |
| 175 |
|
| 176 |
Example parsing: |
| 177 |
|
| 178 |
|
| 179 |
|
| 180 |
|
| 181 |
-- |
| 182 |
gentoo-commits@g.o mailing list |
Archives