PLD-doc: devel-hints-en.txt - notes on Release tag and %rel macro

[pawelz]

Author: pawelz                       Date: Mon Jun  7 09:40:17 2010 GMT
Module: PLD-doc                       Tag: HEAD
---- Log message:
- notes on Release tag and %rel macro

---- Files affected:
PLD-doc:
   devel-hints-en.txt (1.50 -> 1.51) 

---- Diffs:

================================================================
Index: PLD-doc/devel-hints-en.txt
diff -u PLD-doc/devel-hints-en.txt:1.50 PLD-doc/devel-hints-en.txt:1.51
--- PLD-doc/devel-hints-en.txt:1.50	Mon Jun  7 11:00:46 2010
+++ PLD-doc/devel-hints-en.txt	Mon Jun  7 11:40:12 2010
@@ -87,7 +87,17 @@
 
 3. Package versioning
 
-3.1 Application version vs. package Version and Release tags
+3.1 Release tag
+
+   Release: tag is internal PLD package version number. In most cases it is
+   independent from upstream version number (see next paragraph for
+   exceptions).
+
+   Fractional release (0.1, 0.5, 3.14 etc) means package is not yet ready to
+   be sent to builders. If you think that package is ready to be build,
+   increase release to the next integer.
+
+3.2 Application version vs. package Version and Release tags
 
    For full releases the Version field contains the package version.
    For development or testing version (CVS snapshots, alpha, beta,
@@ -97,13 +107,19 @@
    versions it will look like 0.rcX.1 and for snapshots 0.2003.0303.1).
    An example definition (real version: 2.0rc1):
    Version:	2.0
+   %define		rel		1
    %define		rcver	rc1
-   Release:	0.%{rcver}.1
+   Release:	0.%{rcver}.%{rel}
+
+   In this case when we change the spec file for the same software version we
+   must just bump the last digit (i.e. %rel macro) in Release ("0" stays the
+   same!)
 
-   In this case when we change the spec file for the same software version
-   we must just bump the last digit in Release ("0" stays the same!)
+   The %rel macro appeared only to make automatic release bump an easy thing
+   (see packages/relup.sh) in case when Release: contains many macros,
+   conditions and such stuff.
 
-3.2 Package Epoch tag
+3.3 Package Epoch tag
 
    You shouldn't use %{epoch} when the package doesn't have Epoch: as such
    defined.
================================================================

---- CVS-web:
    http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/PLD-doc/devel-hints-en.txt?r1=1.50&r2=1.51&f=u