PLD-doc: devel-hints-en.txt - reference only template specs in apa...

[glen]

Author: glen                         Date: Sun Oct  2 11:49:50 2005 GMT
Module: PLD-doc                       Tag: HEAD
---- Log message:
- reference only template specs in apache sections, as the individual packages may discard or change the triggers
- other texts

---- Files affected:
PLD-doc:
   devel-hints-en.txt (1.18 -> 1.19) 

---- Diffs:

================================================================
Index: PLD-doc/devel-hints-en.txt
diff -u PLD-doc/devel-hints-en.txt:1.18 PLD-doc/devel-hints-en.txt:1.19
--- PLD-doc/devel-hints-en.txt:1.18	Fri Jul 15 19:04:09 2005
+++ PLD-doc/devel-hints-en.txt	Sun Oct  2 13:49:45 2005
@@ -67,6 +67,12 @@
 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!)
 
+Note: it is not neccessary to include leading "0." if the release starts with
+non-numeric, like "RC2", because letters make smaller release than numbers:
+$ rpmvercmp 1.6.0-RC2 1.6.0-1
+1.6.0-RC2 < 1.6.0-1
+but this is not widely accepted, at least nobody on irc but me liked this :)
+
 Package groups:
 A package must have a defined Group field according to SOURCES/rpm.groups
 
@@ -560,8 +566,9 @@
 Apache version independant packages
 
 As of 1.3.33-2 version, apache1 also supports confdir based configuration.
-To make your package require just apache functionality (versionless
-dependancy), You should add to your package:
+To make your package require just apache functionality (apache version
+independant dependancy ie apache1 or apache2 are both ok), You should add to
+your package:
 Requires:	apache >= 1.3.33-3
 
 If your package needs some apache core module, add virtual dependancy:
@@ -570,18 +577,23 @@
 To place apache configuration for both apaches, You should first put the
 apache configuration in your application config directory (not to apache
 dir as it might not exist!). %{_sysconfdir}/apache-%{name}.conf is good choice.
+If your application owns (has) %{_sysconfdir}, it's perhaps better call it
+%{_sysconfdir}/apache.conf
 
 Please see template-apache-package.spec for implementation of the triggers.
 
 If your application did mungle apache.conf or httpd.conf earlier, You must add
-trigger to convert to new schema. (it's usually with apache1 applications)
-You can see sample trigger from template-apache1_module.spec
-For apache2 trigger see turba.spec
-also template-apache-package.spec contains sample trigger for migration.
+trigger to convert to new schema. See template-apache-package.spec for sample
+triggers for migration.
+
+for apache1 modules there's template: template-apache1_module.spec
 
 If your application apache config was previously in apache directory, then you
-should also add trigger when moving it. see imp.spec for sample trigger. also
-template-apache-package.spec should have the sample.
+should also add trigger when moving it. see template-apache-package.spec for
+the samples.
+
+
+
 
 Naming files in SOURCES.
 few unexplained conventions (if smb knows, plz explain the reasons):
@@ -593,6 +605,7 @@
 
 maybe it's because it's convinient to vi ../SOURCES/NAME-<TAB> to get list of
 patches and vi ../SOURCES/NAME.<TAB> to get your shell expand config files.
+
 
 
 PERL
================================================================

---- CVS-web:
    http://cvs.pld-linux.org/PLD-doc/devel-hints-en.txt?r1=1.18&r2=1.19&f=u