SOURCES naming (devel-hints-en)

[Paweł Sakowski]

glen committed:
> Naming files in SOURCES.
> few unexplained conventions (if smb knows, plz explain the reasons):
> - 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

The reasons, off the top of my head:
- to decrease entropy (it's good to have _a_ policy, this one is just
  as good as any other)
- for grouping files in SOURCES (as in `rm SOURCES/galeon*` or visual
  inspection of `ls`)
- to avoid filename conflicts between packages by prefixing (half the
  specs could want to use the name ac_am-fix.patch)
- to easily determine visually which package a given source belongs to
  (by the filename prefix)

-- 
Paweł Sakowski <saq at pld-linux.org>
PLD Linux Distribution