
$Id: TODO 228 2005-02-13 16:01:03Z joostvb $

- Split requirements in manual in cvs-build-time, build-time and run-time;
  document all run-time dependencies, get configure.ac check for them.
- Don't use pod but docbook for st_snapshot manpage (or wait for Laurent to
  do this).
- Write a systraq(8) manpage (or wait for Laurent to do this).  Remove details
  about this script from the systraq manual.  Copy stuff from NEWS file.
- Finish systraq manual: add diagram listing dependencies (see the FIXME)
- Don't install st_snapshot.hourly in bin/ , but in a location like libexec/ .
- Don't use md5sum, but sha1sum as shipped with GNU coreutils
  ( ftp://ftp.gnu.org/gnu/coreutils/ ).  Interface seems same, so change
  should be trivial.
  md5sum should be variable ST_SUM in /usr/sbin/systraq, it should be set
  optionally.
- The way all homedirectories are found is braindead.  It fails in case
  something like NIS is used.  Document this.
- Check systraq announcement on http://directory.fsf.org/, update systraq
  webpage.
- Systraq should silently ignore non-world-readable to-be-monitored files in
  homedirectories.  This is nice on systems where some users like to have e.g.
  ~/.bashrc monitored and others do not.  Document this behaviour, and instruct
  admins to check for readability when setting up list of to be monitored
  files.  Check what happens when permissions change: are we getting warned?  I
  guess we should be warned.  Bug reported by Lionel Elie Mamane.
- Make this package usable on systems with a configured filetraq:
  > What to do with filetraq.default
  > What to do with filetraq cron job
- Guess systraq doesn't need it's own group, but is fine with being in
  'nogroup'.  systraq files can be group-owned root.

