[gentoo-commits] proj/devmanual:master commit in: ebuild-writing/file-format/

["Markos Chandras" <hwoarang@gentoo.org>]

commit:     b4972b20f9dae97f6b86d2da51f8831bce6c625e
Author:     Chris Reffett <creffett <AT> gentoo <DOT> org>
AuthorDate: Sat Jan  4 19:51:21 2014 +0000
Commit:     Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Sat Jan  4 19:51:21 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=b4972b20

Further changes to ebuild naming, clarify snapshot naming scheme

---
 ebuild-writing/file-format/text.xml | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/ebuild-writing/file-format/text.xml b/ebuild-writing/file-format/text.xml
index cffb9e4..aa76952 100644
--- a/ebuild-writing/file-format/text.xml
+++ b/ebuild-writing/file-format/text.xml
@@ -99,7 +99,8 @@ Finally, version may have a Gentoo revision number in the form <c>-r1</c>. The i
 Gentoo version should have no revision suffix, the first revision should be
 <c>-r1</c>, the second <c>-r2</c> and so on. See <uri link="::general-concepts/ebuild-revisions"/>.
 Revision numbers are distinguished from patch releases by revision bumps being
-changes by Gentoo developers, while patch releases are new releases by upstream.
+changes by Gentoo developers, while patch releases are new releases by upstream (with the exception
+of snapshots, see below).
 </p>
 
 <p>
@@ -107,8 +108,11 @@ Overall, this gives us a filename like <c>libfoo-1.2.5b_pre5-r2.ebuild</c>.
 </p>
 
 <p>
-When packaging a snapshot of a source repository, the standard naming format is
-$(last-released-version)_pYYYYMMDD
+When packaging a snapshot of a source repository, there are two commonly used formats. The first
+treats the snapshot as a patch to the previous version, and so the ebuild version is in the format
+$(last-released-version)_pYYYYMMDD. Alternatively, the snapshot may be treated as a pre-release to
+an upcoming version, usually used when a release is anticipated but not out yet. The format for this
+is $(upcoming-version)_preYYYYMMDD.
 </p>
 
 </body>