Author: qboosh Date: Sat Jun 16 20:17:29 2007 GMT
Module: PLD-doc Tag: HEAD
---- Log message:
- don't suggest underscore insanity
---- Files affected:
PLD-doc:
devel-hints-en.txt (1.28 -> 1.29) , devel-hints-pl.txt (1.47 -> 1.48)
---- Diffs:
================================================================
Index: PLD-doc/devel-hints-en.txt
diff -u PLD-doc/devel-hints-en.txt:1.28 PLD-doc/devel-hints-en.txt:1.29
--- PLD-doc/devel-hints-en.txt:1.28 Tue Jun 12 18:38:01 2007
+++ PLD-doc/devel-hints-en.txt Sat Jun 16 22:17:24 2007
@@ -60,9 +60,9 @@
we put a 0.<pre-version>.<real release> (eg. for rcX and/or beta
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 _rc rc1
-Release: 0.%{_rc}.1
+Version: 2.0
+%define rcver rc1
+Release: 0.%{rcver}.1
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!)
================================================================
Index: PLD-doc/devel-hints-pl.txt
diff -u PLD-doc/devel-hints-pl.txt:1.47 PLD-doc/devel-hints-pl.txt:1.48
--- PLD-doc/devel-hints-pl.txt:1.47 Tue Jun 12 18:38:01 2007
+++ PLD-doc/devel-hints-pl.txt Sat Jun 16 22:17:24 2007
@@ -80,8 +80,8 @@
rc2 i beta b�d� to 0.rc2.1, dla snapshot�w ci�g typu 0.20030303.1).
Przyk�adowy opis w specu (wersja rzeczywista: 2.0rc1)
Version: 2.0
-%define _rc rc1
-Release: 0.%{_rc}.1
+%define rcver rc1
+Release: 0.%{rcver}.1
W takim przypadku po zmianach speca dla tej samej wersji oprogramowania
zwi�kszamy ostatni� liczb� w Release ("0" pozostaje bez zmian!).
================================================================
---- CVS-web:
http://cvs.pld-linux.org/PLD-doc/devel-hints-en.txt?r1=1.28&r2=1.29&f=u
http://cvs.pld-linux.org/PLD-doc/devel-hints-pl.txt?r1=1.47&r2=1.48&f=u
_______________________________________________
pld-cvs-commit mailing list
[email protected]
http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit
