--- xml/htdocs/proj/en/glep/glep-0054.html 2007/12/17 21:10:03 1.6 +++ xml/htdocs/proj/en/glep/glep-0054.html 2008/01/06 02:08:59 1.7 @@ -1,11 +1,7 @@ - + @@ -21,7 +17,7 @@ border="0" width="150" height="35" /> [Gentoo Linux Home] -[GLEP Index] +[GLEP Index] [GLEP Source] @@ -69,18 +65,18 @@

Motivation

-

Currently there is no standard way of marking SCM ebuilds. Using 9999 as the +

Currently there is no standard way of identifying SCM ebuilds. Using 9999 as the version is pretty common, but it is handled like any other ebuild and hence portage cannot provide any additional features for packages with such a version. -Another way is adding separate package with -cvs suffix in its name, but that -forces to use || ( cat/pkg cat/pkg-cvs ) dependencies. The closest to what -is proposed in this GLEP is the cvs version part, but its implementation is -of very limited use. It has strange comparison rules, no documentation, has -never been used in the tree and has a misleading name.

+Another way is adding a separate package with a -cvs suffix in its name, but +that forces the author to use || ( cat/pkg cat/pkg-cvs ) dependencies. The +closest to what is proposed in this GLEP is the cvs version part, but its +implementation is of very limited use. It has strange comparison rules, no +documentation, has been used sparingly (if ever) and has a misleading name.

The possibility for package managers to recognise SCM ebuilds would allow them to add features dedicated specially to said ebuilds. One such feature could be -automatic re-installation of SCM packages once a day or week, but that's beyond -this GLEP.

+automatic re-installation of SCM packages once a day or week. Any +specifications for such features are beyond the scope of this GLEP.

Specification

@@ -105,11 +101,16 @@

Example parsing:

@@ -184,7 +185,7 @@