PLD-doc: devel-hints-en.txt - updates to naming files to SOURCES

[glen]

Author: glen                         Date: Sun Oct  2 15:30:34 2005 GMT
Module: PLD-doc                       Tag: HEAD
---- Log message:
- updates to naming files to SOURCES

---- Files affected:
PLD-doc:
   devel-hints-en.txt (1.20 -> 1.21) 

---- Diffs:

================================================================
Index: PLD-doc/devel-hints-en.txt
diff -u PLD-doc/devel-hints-en.txt:1.20 PLD-doc/devel-hints-en.txt:1.21
--- PLD-doc/devel-hints-en.txt:1.20	Sun Oct  2 17:12:51 2005
+++ PLD-doc/devel-hints-en.txt	Sun Oct  2 17:30:28 2005
@@ -596,15 +596,25 @@
 
 Naming files in SOURCES.
 
-few unexplained conventions (if smb knows, plz explain the reasons):
+few unexplained conventions:
 - NAME-foo.patch - patches
 - NAME.cron - cron fragments which go to /etc/cron.d dir
 - NAME.logrotate - logrotate config whichgoes to /etc/logrotate.d
 - NAME.sysconfig - application cofing which goes to /etc/sysconfig
 - NAME.init - initscript which goes to /etc/rc.d/init.d
 
-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.
+NAME could be package %{name} or real name of package if it's prefixed with
+group like, php-pear-%{_pearname}, perl-%{pnam}, python-%{_name}. Having
+patches sources prefixed with package name also avoids file collisions between
+different packages.
+
+one of the reasons is 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.
+
+please try to follow this, as then if there's planned massive changes to all
+crontab, initscript or sysconfig files, then the files are easily located from
+CVS.
 
 
 PERL.
================================================================

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