Hi to all,

I've prepared a new Debian package.  This version will probably be the one
which you'll find in Sarge/stable.

There are some invasive changes in this version which call for a serious
test.  In accordance with a suggestion, I've changed the configuration
mechanism.  For details, please read the NEWS.Debian file attached.

Could the Debian users who follow this forum test it and give some feedback?
You can download the package from the following link:

  http://l10n-turkish.alioth.debian.org/debian/elog_2.5.8+r1592-1_i386.deb

Thanks in advance for your participation,

elog (2.5.7+r1589-1) unstable; urgency=low

  * Starting from this version, /etc/default/elog is installed as part
    of the package.  Following variables (with default values) can
    be used in /etc/default/elog:

      # Host where elogd will run.
      # HOST=localhost

      # Be verbose.
      # VERBOSE=yes

      # Port where elogd will run.
      PORT=8080

      # Logbook root directory.
      LOGBOOKDIR=/var/lib/elog

      # Resource directory (i.e. themes, icons).
      RESOURCEDIR=/usr/share/elog

    These variables will become the command line options of elogd.
    Since command line options always supersede the corresponding
    options in config file, the existence of such a file provides a
    way to discriminate two roles: System admin (root) and Elog admin.
    Elog config file (/etc/elog.conf) now represents the Elog admin's
    settings, while /etc/default/elog corresponds to the system admin's
    settings.  For example, if system admin defines the following line,
    the Elog admin's port setting in config file will be ignored and
    ELOG will always listen port '80' (note that the compiled-in
    default port is '8080'):

      PORT=80

    One can also change the logbook repository location by using the
    same mechanism, e.g. to set the data directory as '/srv/elog' (as
    suggested in FHS v2.3) use the following line:

      LOGBOOKDIR=/srv/elog

    Maintainer scripts should gracefully handle this transition.  But
    please note that those system admin's settings listed above should
    not be used in elog.conf, even though Elog allows it.

 -- Recai OktaÅŸ <roktas@omu.edu.tr>  Sun, 20 Mar 2005 05:09:57 +0200