A recent syslog-ng (OpenSuSE Tumpleweed, syslog-ng 3.7.1) complained because
of the strange and conflicting source definitions used here. In my opinion all
messages are simply passed internally. No need to tcp or /dev/log. Anyway, the
quickfix here makes things go well.

binary installation directory is hard-wired;
use variable name CSBACKBINDIR instead of LOCBINDIR to avoid conflicts with
Seitosh

increment operator was not working as expected

They way a list of dictionary keys were extracted apparently was not correct

improve implementation of csbucscheck.sh by
- providing proper command line reading
- providing proper usage information
- providing comments in the code
- providing additional command line options to select an output directory and
  checksum binary executable

The purpose of csbucheckcsfiles.sh is covered by the functionality of
csbucscheck.sh

Rename checksum check script.

csback_cscheck.sh
is designed to recurse into a subdirectory tree and to verify checksums
therein. It was originally created to check the LSDF archive.

package creation is obsolete since csback is publish through gitlab which
provides its own mechanism of tarball creation.

All options in the mail section which are no longer mandatory to csbackntfy.py
are no longer expected by csback2cron.py but are just evaluated, if provided
in the config file. No consistency checks are performed. A such created
crontab entry still may be rejected by csbackntfy.py

add comment and remove svn keywords