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

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

commit:     ba2e7aa36d41c7a4e2caacd50bb2ae482934b23c
Author:     Chris Reffett <creffett <AT> gentoo <DOT> org>
AuthorDate: Sat Jan  4 02:50:18 2014 +0000
Commit:     Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Sat Jan  4 19:39:59 2014 +0000
URL:        http://sources.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=ba2e7aa3

Clarify difference between _p and -r in ebuild names wrt bug 414867,
also mention the normal way of naming snapshots

---
 ebuild-writing/file-format/text.xml | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/ebuild-writing/file-format/text.xml b/ebuild-writing/file-format/text.xml
index 9d00e6b..cffb9e4 100644
--- a/ebuild-writing/file-format/text.xml
+++ b/ebuild-writing/file-format/text.xml
@@ -70,7 +70,7 @@ what portage considers to be the 'lowest' version comes first.
   </tr>
   <tr>
     <ti>_p</ti>
-    <ti>Patch level</ti>
+    <ti>Patch release</ti>
   </tr>
 </table>
 
@@ -98,12 +98,19 @@ No integer part of the version may be longer than 18 digits.
 Finally, version may have a Gentoo revision number in the form <c>-r1</c>. The initial
 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.
 </p>
 
 <p>
 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
+</p>
+
 </body>
 </section>